MCP connection and capabilities
MCP lets an AI client use Re:Activity tools to work with your activities and content plans. Connect with an agent key or by signing in from the client.
Get started#
You can connect in two ways: with a key, or by signing in from the client.
- Create a key
rca_*in agent key settings and select the permissions your task needs. Copy the secret when it is issued; it is shown only once. Revoke and replace the key if it is lost or exposed. Connect it with the connection instructions using anAuthorization: Bearerheader. Do not put the secret in your prompt. - If the client supports OAuth, sign in from the client. Do not put a secret in the client config: you confirm permissions on the consent page. The page is described under Connect.
- Describe your task to the agent, including the channel, dates and time zone where relevant. Ask it to clarify missing details.
Activity tools require a live key and a Pro or Enterprise plan. An OAuth connection is always a live key, never rca_test_. Existing keys do not receive new permissions automatically. See permissions and plans and the agent key guide.
Activities and content plans#
An agent can read activities, prepare their drafts, and request a launch or stop. The activity owner must confirm each launch or stop request in the app; control requests require an Enterprise live key. An agent can also prepare content plan posts with separate permissions. See activity workflows and permissions and capabilities.
Example prompts#
Start with “Create an activity draft for my channel and ask me for any missing details.” Find three detailed prompts in activity examples.
For integration developers#
The activity tools support reading, draft editing and action requests. See activity tools and write requirements.
Connect#
The address is https://reactivity.me/mcp (Streamable HTTP).
A key is sent as Authorization: Bearer <agent key>. In the examples it is read from an environment variable: export REACTIVITY_AGENT_KEY="<your key>". Keep the key out of public configuration and screenshots.
With OAuth you confirm permissions on the consent page the client opens, and do not put a secret in the client config. The page title is "Connection". The page shows the application name and the redirect host. content:read and activities:read are already checked when the plan allows them. content:draft, content:publish, generate:image, activities:draft and activities:control stay off until you check them. The default mode is review. The buttons are Allow and Deny. The connection lasts until you revoke it. It is always a live key, never rca_test_.
Choose your client below.
Claude#
claude mcp add --transport http reactivity https://reactivity.me/mcp \
--header "Authorization: Bearer $REACTIVITY_AGENT_KEY"
ChatGPT#
The chatgpt.com window does not take a permanent key in a header. The connection uses OAuth, and you do not copy a secret.
- Open Plugins, click Add, and choose Add custom MCP server.
- Enter a name and the address
https://reactivity.me/mcp. Authentication is OAuth. - Accept the warning and create the plugin, then click Connect.
- Sign in to Re:Activity if the browser is not signed in yet. On the consent page, check the permissions and click Allow. Read is already checked when the plan allows it; write, image generation, and launch stay off until you check them.
- In a new chat, mention the plugin with
@and describe the task.
Revoke the connection in agent key settings, section Connections.
A key still works with ChatGPT through the OpenAI Responses API: if you write your own code or agents on OpenAI models, add Re:Activity to the request as an MCP tool (substitute the value of $REACTIVITY_AGENT_KEY in your code from the environment variable):
{ "type": "mcp", "server_label": "reactivity", "server_url": "https://reactivity.me/mcp",
"headers": { "Authorization": "Bearer $REACTIVITY_AGENT_KEY" }, "require_approval": "never" }
Gemini#
For Gemini CLI:
gemini mcp add --transport http -s user \
--header "Authorization: Bearer $REACTIVITY_AGENT_KEY" reactivity https://reactivity.me/mcp
Or in the file ~/.gemini/settings.json (put the key value in place of $REACTIVITY_AGENT_KEY):
"mcpServers": { "reactivity": { "httpUrl": "https://reactivity.me/mcp",
"headers": { "Authorization": "Bearer $REACTIVITY_AGENT_KEY" } } }
Hermes#
In ~/.hermes/config.yaml or ~/.hermes/profiles/<profile>/config.yaml.
Key (put the key value in place of $REACTIVITY_AGENT_KEY):
mcp_servers:
reactivity:
url: https://reactivity.me/mcp
headers:
Authorization: Bearer $REACTIVITY_AGENT_KEY
timeout: 120
Sign-in from the client: no Authorization header, and auth: oauth. The client opens the browser for consent. Sign-in starts with hermes mcp login reactivity.
mcp_servers:
reactivity:
url: https://reactivity.me/mcp
auth: oauth
timeout: 120
OpenClaw#
With a command or via the Control UI (Settings, MCP section):
openclaw mcp add reactivity --url https://reactivity.me/mcp --transport streamable-http
In the config the server lives under mcp.servers.reactivity: fields url and transport: "streamable-http". For a key, set the header Authorization: Bearer ${REACTIVITY_AGENT_KEY} and do not set auth: oauth: with OAuth the static header is ignored. For sign-in from the client, set auth: oauth and do not set a static Authorization header. Check the connection:
openclaw mcp doctor reactivity --probe
What the agent sees#
After connecting, the agent sees the content_plan_* tools and, with activities:read, activities_list and activities_get, and with activities:draft the activities_draft_* tools - only those your key has permissions for. An Enterprise live key with activities:control can also request a launch or stop and check the request status. The activity owner must confirm each request; content-plan approval modes do not change this requirement. For example, a key with content:read gets listing and viewing only. The tools cover viewing plans, posts and channels, creating and importing a plan, adding, editing and deleting items, uploading an image, sending for approval, scheduling and unscheduling, generating an image and checking its status.
Other clients (Claude Desktop, Cursor, and so on) connect by adding a remote MCP server over HTTP with a custom authorization header; the exact menu name depends on the app.
Troubleshooting#
Check the address and Bearer key, and ensure the key has not expired or been revoked. If a tool is missing, check its permission and plan in permissions and capabilities. Activity tools require a live key; control requests also require Enterprise. You can also launch or stop an activity in the app. For 429, wait before retrying. See the error table for other codes and remedies.
If the sign-in is stale, the client refreshes it itself. You do not copy a new secret. If the connection was revoked or the refresh fails, start sign-in from the client again.
Revoke a connection in agent key settings, section Connections. No secret is shown there. Revoking takes effect immediately.