Quickstart
Create your organization, connect your first MCP server and ask your first question, in about ten minutes.
You need an MCP server that sremcp can reach over https. If you don't have one yet, the GitHub and Sentry servers are hosted by their vendors, so there's nothing to run.
Sign in
Open app.sremcp.com and Continue with Google, or sign up with your email and a password.
Start an organization
On Start an organization, enter an Organization name (for example Acme SRE) and click Create organization. You become its Owner.
If a teammate already invited you, you'll see You've been invited instead: click Accept and open to join with the role they gave you.
Onboard an MCP server
Go to MCP servers and click Onboard server. Fill in:
- Display name and Slug: the slug appears in tool names, like
mcp__github__get_commit. - Endpoint URL: the server's MCP endpoint, for example
https://api.githubcopilot.com/mcp/readonly. - Transport: Streamable HTTP for almost every server today. Pick SSE (legacy) only for servers that offer nothing else.
- Authentication: how the server checks who's calling. See Authentication.
Click Save as draft. The server's page opens.
Connect (OAuth servers only)
If you chose OAuth (sign in with the server), click Connect in the Sign-in (OAuth) panel and sign in on the server's page. Every call to that server will act as the account you signed in with.
Test the connection
Click Test connection. sremcp lists the server's tools under Discovered tools, all pending.
Approve tools
Tick the tools the agent may call (Select read-only ticks every tool the server marks read-only), then click Save approvals. See Approve tools.
Grant roles and activate
Under Role access, tick the roles that should use this server and click Save access. Owners, Admins and SREs always have every server. Then click Activate.
Investigate
Go to Investigate and ask, for example, Summarize activity in the last 12 hours. You'll see each tool call as it runs, then the answer.