MCP integration

Recognise your team without leaving your editor

One OAuth connection and your team can read the feed and draft applauds from Cursor or Claude. Standard MCP, so it works with whatever they switch to next.

Stay where you areRead the feed and draft applauds from the tool you already have open. No new tab, no context switch.

OAuth, not API keysAuthorization code with PKCE. Tokens never appear in a redirect URL and your client refreshes them for you.

Your permissions follow youA member connecting a client is still a member. Admin tools stay blocked at the permission layer.

MCP server hostThis is our app URL. Snippets below use it as the MCP endpoint.

Before you start

An account in an organisationYou connect as yourself. Tools act in whichever organisation is current for you.

A client that speaks MCPCursor and Claude Code are the two we test against. Anything that implements MCP over HTTP works.

Your organisation on the partner allowlistRequired in production. An admin can request it from Settings → Integrations → MCP; in local development every org is allowed.

Connect your platform

Pick what your team uses. All of them hit the same endpoint with the same OAuth flow — only the setup step differs.

Point Cursor at the serverSettings → MCP → Add new server, or edit the config file directly. The URL is all Cursor needs — no token lives in the file.

~/.cursor/mcp.json

{
  "mcpServers": {
    "the-remote-suite": {
      "url": "https://dev.theremotesuite.com/api/mcp"
    }
  }
}

Authenticate onceCursor shows an Authenticate button next to the server. It opens our consent screen: sign in, pick which organisation the tools act in, choose scopes.

Cursor stores and refreshes tokens itself. You never paste an access token, and it never appears in a redirect URL.

Work without switching tabsAsk in Cursor: “who on my team hasn’t been recognised this month?” or “draft an applaud for Ankur”. Tools run in your current organisation — the same one the web app shows.

Working across several orgs? The orgs_switch tool changes the current one, with a confirm in chat.

Check it worked

Ask for the tool list. You should get back the read and draft tools your scopes allow.

Terminal

curl -s -X POST "https://dev.theremotesuite.com/api/mcp" \
  -H "authorization: Bearer $ACCESS_TOKEN" \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A working connection lists tools for posts, leaderboard, values, claps and drafts. An empty list almost always means the scopes were narrowed on the consent screen — reconnect and pick more.

Scopes

You choose these at consent. Your role in the app still applies on top — connecting a client never widens what you’re allowed to do.

mcp:readEverything you can already see: posts, comments, values, clap policy and balances, leaderboard, badges, notifications, celebrations.

postsleaderboardachievementscelebrations

mcp:draftGenerates post text and draft applauds. A draft is not a post — nothing is published under this scope.

draftstext generation

mcp:writePublishes posts and comments, sets reactions, and — for admins only — invites, roles, clap allocation and company values. Each call confirms in chat first.

postscommentsmembersclaps

Writes are confirmed, never silentWrite tools ask your client to confirm before they run. Admin-only actions — invites, roles, clap allocation, company values — stay blocked for members at the permission layer, exactly as in the app.

Limits and errors

120 req/minPer organisation and user on the MCP endpoint. Exceeding it returns a rate-limit error — back off and retry.

Token lifetimeAccess tokens are short-lived. Refresh with grant_type=refresh_token; Cursor and Claude Code handle this for you.

403 on a revoked grantOnce a grant is revoked in Settings, the next call fails. Reconnect from your client to get a fresh one.

MCP_ORG_DISABLEDYour organisation is not on the production partner allowlist. Consent will succeed and tool calls will fail — ask an admin to request access.

One org at a timeTools act in your current organisation. Switching is an explicit tool call, and chat history is not merged across organisations.

Revoke access

In the app: Settings → Integrations → MCP, then remove the grant. The next call with it returns 403. From the terminal:

Terminal

curl -s -X POST "https://dev.theremotesuite.com/api/mcp/oauth/revoke" \
  -d "token=$REFRESH_TOKEN&client_id=YOUR_CLIENT_ID"

Stuck on the connection?Send the error code and which platform you’re on — a person answers.

support@theremotesuite.com