Skip to main content
What you’ll get: your IDE can ask ewake who owns a service, what it depends on, and what ewake already found the last time that service broke, without you leaving the editor or opening Slack.
Ewake exposes a remote MCP server (Model Context Protocol) at /mcp on your ewake instance.
This page is about querying ewake from an MCP client. To connect an MCP server of your own to ewake, so it can call your tools during investigations, see Custom MCP Server.

​
Prerequisites

  • An ewake instance reachable from your machine (e.g. https://your-company.ewake.ai)
  • An MCP client that supports remote servers over HTTP, Claude Code and Cursor both do
  • An ewake account, for the browser sign-in during the connection

​
Connect your client

The connection uses OAuth: your client registers itself, sends you to your ewake dashboard to approve, and receives its own token. You never copy or paste a key.
Then run /mcp inside Claude Code and pick ewake to start the sign-in.

​
Approve the connection

1

Your browser opens on the ewake approval page

The client sends you to the authorization endpoint on your ewake instance. If you’re not signed in, you go through the normal dashboard login first and come back to the same page.
2

Review what the client is asking for

The page names the client, what it will be able to do (read your service map, ownership and incident history), and the address it will send you back to. Check that address is your client, then click Approve.
3

You land back in your client

The server shows as connected and its four tools are listed. Ask it something, for example: “Who owns the checkout service?”

​
Alternative: connect with an API key

Use an API key when nobody can click Approve, a CI job, a script, or a container. It authenticates as your company rather than as a person.
1

Create the key

In your ewake dashboard, open API Keys in the sidebar and create a key. Copy it, it’s shown once and starts with ew_.
2

Send it as a bearer token

An API key is a shared credential, treat it like a password. It is also workspace-wide, not scoped to MCP: the same key can post deployment events. Prefer OAuth for anything a human uses, so calls are attributable to a person and revoking access doesn’t affect anyone else.

​
What to ask

The tools compose, so you ask the question and the client chains the calls:

​
Security

  • Read-only. Every tool is a query. Nothing on the MCP server creates, edits or deletes anything in ewake or in your integrations.
  • Scoped to your company. Both authentication paths verify that the caller belongs to this instance’s company before the request reaches a tool.
  • Your credential never reaches the tools. The transport passes an identifier, not the API key or the access token.
  • Deactivated users lose access immediately, their token stops validating on the next call.

How ewake handles permissions and data →

Something you want to reach from your editor that isn’t here? Tell us at support@ewake.ai, the tool surface grows from what people ask for.