Use an MCP server with an API key in Claude
Many MCP servers already run on the internet – as a WordPress plugin, in n8n or self-built – and only accept an API key. Handing that key to everyone on the team is risky, and not every AI client can send it. The XenMCP OAuth bridge turns it into an address with OAuth: everyone signs in individually, the key stays with us.
At beta launch
- 1
Enter address and key
Your server’s URL and the kind of key: bearer token, a custom header such as
X-API-Key, user and password (e.g. WordPress application passwords) or a parameter in the URL. - 2
Test the connection
XenMCP connects to your server and shows its tools. Only then is it saved.
- 3
Get an address with OAuth
For example
https://wp-acme.xenmcp.com/mcp. You add this address to Claude as a connector. - 4
Sign in and allow
Claude opens the XenMCP sign-in. After “Allow”, Claude works with your server – in the browser, in the desktop app and on your phone.
Safe for teams, too
- The key stays with XenMCP: encrypted (AES-256-GCM), never shown again, never passed to the AI client.
- Everyone signs in individually. Whoever leaves the team loses access – the key does not have to change.
- The log shows who called which tool and when – without content.
- Gateway in Germany. Your server needs no changes and gets no new credentials.
Without XenMCP?
For a single person, the key directly in the client is often enough: in Claude Code, Cursor and VS Code you add a header yourself, and Claude connectors can now – depending on the plan and still in beta – send headers, too. Then everyone shares the same key, though, and whoever leaves takes it with them. Also check whether your server already offers OAuth itself; n8n and some WordPress plugins can do that now. The bridge pays off when several people need access, when access must be revocable and traceable per person, or when your client does not support headers.
Ready for your first connector?
The beta is free. Sign up and tell us which systems you want to connect.
Join the waitlist