Skip to main content
What you’ll get: ewake can consult a tool surface you own — an internal API, a bespoke log store, a service catalog — during an investigation, alongside its built-in integrations. If you can expose it over MCP, ewake can query it.
This page is about connecting your MCP server to ewake. For the reverse — querying ewake from Claude Code, Cursor, or another MCP client — see MCP Server.

​
Prerequisites

  • An MCP server reachable over HTTPS, using streamable HTTP transport
  • A publicly reachable URL for it (through a tunnel such as Cloudflare Tunnel or ngrok if it lives inside your network)
  • Read-only credentials for whatever the server talks to

​
Configuration

1

Expose your MCP server over HTTPS

Ewake calls your endpoint outbound; there are no inbound ports to open on ewake’s side. Point it at a stable URL, for example https://mcp.yourcompany.com/logs/mcp.
2

Open the Custom MCP integration in ewake

In your ewake dashboard, go to Integrations → Custom → Custom MCP → click Connect a server.
3

Describe the server

The Description is not decoration. Ewake uses it to decide whether to consult this server during an investigation. A vague description means the server rarely gets called.
4

Add request headers

Under Request headers, add whatever your endpoint requires — an Authorization bearer token, or a Cloudflare Access service token (CF-Access-Client-Id and CF-Access-Client-Secret).Values are stored encrypted.
5

Test the connection and pick the tools

Click Test connection. Ewake lists every tool the server advertises and asks which ones it may call.Use Select read-only to tick the tools whose names look read-only (list…, get…, search…, query…, and similar), then adjust by hand.
Ewake can only call the tools you tick here — nothing else the server exposes, even if it adds tools later. New tools are not auto-approved; come back and tick them.
6

Save

Click Save.
The server is connected. Ewake will consult it during investigations when the description matches what it’s looking for.

​
Connect more than one server

Custom MCP is a multi-instance integration: connect as many servers as you need, each with its own name, description, headers, and tool allowlist. They appear as separate entries under Connected servers, and you can disconnect one without affecting the others. Give each a distinct description — that’s what ewake matches on when deciding which server to consult.

​
Security

  • You choose the tools. The allowlist is enforced on ewake’s side; unticked tools are never called.
  • Connect with read-only credentials. The allowlist is a guardrail, not a substitute — read-only credentials mean writes are refused at the source even if a tool is mis-ticked.
  • Headers are stored encrypted, the same way integration secrets are.
  • Outbound only. Ewake calls your endpoint; you open no inbound ports to ewake.

How ewake handles permissions and data →

Need help exposing a server? Contact support@ewake.ai.