# Marcora: Brand Context & Writing: Hermes Agent plugin

> Brand context, marketing blueprints, content creation, grounding, and GTM planning through Marcora's hosted MCP server (Streamable HTTP at https://mcp.marcora.ai/, OAuth 2.1 PKCE or Bearer API token).

Canonical: https://hermeswatcher.com/plugins/marcora  
Tier: Community  
Official page (Nous Research): https://hermes-agent.nousresearch.com/docs/plugins/marcora  
Last updated in catalog: 2026-11-17

Brand context, marketing blueprints, content creation, grounding, and GTM planning through Marcora's hosted MCP server (Streamable HTTP at https://mcp.marcora.ai/, OAuth 2.1 PKCE or Bearer API token). Bundles the marcora-mcp workflow skill. Agent Plugins v1 package (plugin.json + mcp.json + skills/), configuration only.

## Good to know before installing

Every tool call goes to Marcora's hosted server (mcp.marcora.ai) over HTTPS and acts on the user's Marcora workspace under their own role; the 63-tool surface (32 read-only, 31 non-read-only, 15 destructiveHint: true) is served at runtime and is not covered by the pinned sha. Non-read-only tools create or update workspace records, send team invitation emails (invite_user), publish share links (create_external_share), or spend team Marcora Studio Credits (create_content with instructions, produce_plan, create_blueprint_draft, create_project with project_brief_instructions, ask_content_assistant, check_content_grounding, trigger_health_audit_scan, convert_markdown_to_word_doc at 2 credits/conversion, and run_workflow). run_workflow starts a server-side automated agent session using Marcora tools and the user's connected third-party apps (allowed_tools is a prompt instruction to the runner, not a separate permission check), workflows that are Active with an On schedule run on Marcora's server-side scheduler independently of the local client, and ask_content_assistant runs an asynchronous background AI assistant that may edit a document in place. The package marks the server untrusted (timeout: 180), so Hermes's host policy prompts before client-initiated calls to tools the server does not mark read-only, though neither Hermes trust nor advisory MCP annotations prevent server-side scheduled workflow runs or background agent actions once started or activated on Marcora.

From the plugin's catalog listing.

## How to install

1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.

```bash
hermes plugins install marcora
```

2. Said no? Turn it on later:

```bash
hermes plugins enable marcora
```

3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see the official page. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins

## Facts

- Category: Cost, speed & monitoring, Work & business
- Maintained by: ccromp (Community)
- Needs: No API keys declared
- Requires Hermes: `>=0.21.6`
- Version: 1.2.26
- In the catalog since: 2026-11-17

## Links

- [Full setup and settings (official page)](https://hermes-agent.nousresearch.com/docs/plugins/marcora)
- [Source code](https://marcora.ai/docs/mcp-overview)
- [All plugins](https://hermeswatcher.com/plugins.md)

---

HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt
