Authentication and access¶
For an ordinary integration service, use a named Ewooks MCP API key in the Authorization header. Your program can run on a schedule without an interactive chat session.
Authorization: Bearer <EWOOKS_MCP_KEY>
Content-Type: application/json
MCP-Protocol-Version: 2025-11-25
Who can enable access¶
The current implementation requires an eligible fleet-owner account, the MCP access entitlement configured by Ewooks, and the owner's explicit enablement of the connection. Account activity, blocking, relevant subscription eligibility and current fleet ownership are checked when authenticating a request.
A general administrator role does not grant access to another owner's fleet. This release selects one eligible owned fleet; multi-fleet selection and delegated company-administrator access are not general-purpose capabilities of this API.
Create a key¶
- Sign in to the Ewooks portal.
- Open AI connections / Tekoäly-yhteydet at
/ai-connections. - Enable the connection for your fleet, if available.
- Create a key with a name identifying the receiving system.
- Copy the key immediately and store it in your backend's secret store.
Keys are shown once. The current lifetime is 90 days, with at most five active, unexpired keys per user. The key grants the current fleet-read access to all four MCP tools; there is no per-tool key-scope selector in this release.
Rotate and revoke¶
Create a replacement key, update your backend, verify it, then revoke the old key. Plan rotation before expiry. Do not recover or reuse a lost key; replace it.
Revocation is checked on each request, including snapshot continuation. Disabling the fleet connection revokes existing API keys and OAuth tokens for that connection. A request already executing cannot be recalled after its response has been sent.
Keep keys out of frontend code, source control, URLs, analytics, support messages and request logs. Use different keys for different receiving services.
OAuth clients¶
The existing OAuth flow is restricted to the supported ChatGPT client. It is not an open registration service for arbitrary partner applications. Third-party server-to-server integrations should use the named API-key approach above unless another flow has been explicitly arranged with Ewooks.
The oauth2 declaration in tool metadata describes the supported OAuth client flow; the endpoint also accepts the ewmcp_ Bearer API keys described here.
Environment separation¶
Create credentials in the environment you use and send them only to its fixed HTTPS endpoint. Do not automatically retry against another hostname or forward Authorization through a redirect. If authentication fails, stop and investigate the key, account and fleet eligibility.