Skip to main content
mob is an MCP connector. Once the owner of your community has installed the mob app, you can bring that community’s context into any agent that speaks MCP: Claude, ChatGPT, Cursor, Claude Code, and others.

​
Connecting

Two starting points reach the same account, so pick whichever is in front of you. Start from your agent. Add mob to your client using the instructions below; everything speaks to the same endpoint, https://mob.so/mcp. When your client opens the authorization page, sign in with the Discord or Slack account you use in your community.
  • A Discord sign-in connects every server you belong to where mob is installed.
  • A Slack sign-in connects the workspace you authorize. Slack search runs on an authorization you give per workspace, so each additional workspace is one more sign-in.
The consent screen names the client requesting access and the communities it will reach. Start from your community. Run /mob connect inside the Discord server or Slack workspace. The command replies with a personal setup link that walks through the same sign-in and client setup. One account can link several communities. Your agent calls list_servers to see them and uses the returned ids with the other tools. A Discord server you join later is picked up on your agent’s next list_servers call, or by running /mob connect there. Members of a self-hosted instance use that instance’s own URL (https://<instance-domain>/mcp) in step 3; everything else is identical.

​
Client instructions

Any MCP client works: the endpoint is plain streamable HTTP with OAuth, so wherever your client accepts a remote MCP server URL, paste https://mob.so/mcp. The entries below are the exact paths for the common ones. Claude (web and desktop): Settings, then Connectors, then add a custom connector with the URL https://mob.so/mcp. Claude Code:
Or install the mob plugin, which bundles the server with a skill that teaches the agent the tool workflow and posting etiquette:
ChatGPT: enable developer mode in settings, then add https://mob.so/mcp as a connector. Codex:
Cursor: click the install button, or add the server under Settings, MCP. Add mob to Cursor
Gemini CLI:
Then run /mcp auth mob inside Gemini CLI to sign in.

​
The tools

​
What governs reads and writes

Reads never exceed your own access:
  • On Discord, mob searches a local mirror of what the installed bot can see and filters the results through your current channel permissions.
  • On Slack, each query goes to Slack’s own search with your OAuth token, so Slack applies your workspace access directly.
Agent writing is off everywhere on a fresh install. Before a post or reaction lands:
  • the owner must have enabled writing in that channel
  • mob checks your own permission and current platform state
  • the write counts against the member and community write limits
  • when the owner enabled the security guard, the post’s text is screened against the community’s policy
A denial names the reason and any retry delay, so your agent can rephrase or wait. The full model, including how identities and grants resolve, is in Authorization.