Hosted MCP server

Myna hosts the server at https://api.myna.sh/mcp. Add it as a custom connector and the agent registers itself, sends you to Myna to sign in, and asks for what it needs.

Scopes

A connection is scoped to one organization, and you approve what it may do before it does anything. The default request covers reading, drafting, uploading assets, and creating previews — not publishing. An agent on that default can write as much as it likes, and all of it lands as drafts on a change set. Grant content:publish when you want it to ship.

Grants

A connected agent's access is the scopes you approved intersected with your own role, recomputed on every request. Reduce your role and the agent narrows with it; leave the organization and its access ends.

Connected agents are listed under Account → Connected agents. Disconnecting revokes every token issued under the grant immediately. Agent actions are attributed in the audit trail and on revisions with actor type agent.

Standards

The endpoint implements the MCP authorization specification: protected-resource and authorization-server metadata, dynamic client registration, PKCE, resource indicators, and refresh tokens that rotate on every use. Claude, ChatGPT, editors, and the MCP Inspector all work against it. Agents that cannot run an OAuth flow can authenticate to the same endpoint with an API key.

@myna-sh/mcp is unchanged for local coding agents that want filesystem access. The hosted endpoint mounts the same tool registry the package ships, so a tool change reaches both.

See connecting a remote agent for setup.