MCP server

AI agents that speak the Model Context Protocol (MCP) — Claude, and many other assistants and coding agents — can work in your workspace through our MCP server:

https://mcp.reminix.com/mcp

Connect

Add the address above as a remote MCP server (in Claude: Settings → Connectors → Add custom connector). The first time, your browser opens:

1. Sign in, if you are not already.
2. Choose one workspace the agent will work in.
3. Choose what it may do. Everything that can change data starts unticked — tick only what the agent needs.
4. Click Allow.

There is nothing to copy and no key to store: the agent receives its own sign-in, valid only for that workspace and that access.

What the agent can do

The agent’s tools are the API operations your choice allows — reading the workspace, listing webhook deliveries, and so on — always as you, with your role in the workspace: if you could not do something in the app, neither can the agent. Everything it changes appears in the workspace’s audit log as you, via the app.

Some things are never available to agents, even with full access — anything that sends your workspace’s data somewhere new or hands out access (for example, creating webhook endpoints or credentials). The agent can ask for them: you approve or deny in the app, and any secret is shown to you, never to the agent — see Approvals.

Stay in control

• Account → Connected apps lists every agent you connected; disconnect one and it stops working immediately.
• Your workspace’s audit log records what each agent did.
• Removing you from the workspace cuts off your agents too.

For developers

The server follows the MCP authorization specification: an unauthenticated request gets a 401 pointing at /.well-known/oauth-protected-resource/mcp, which names the authorization server (https://api.reminix.com/auth, with dynamic client registration and PKCE). Tokens are issued for the MCP server alone. Prefer the command line or the SDK for your own scripts, and see Use with AI agents for the agent skill.