Your Alkemata account

Use your Alkemata account to sign in to the website and connected apps. Open Alkemata account settings to manage your personal details and sign-in methods. If you do not yet have an account, request one here. Project membership and editing rights are assigned separately by project administrators.

Connect an MCP client to Alkemata

An MCP client is an AI assistant that supports a remote Streamable HTTP server. Connect it to the Alkemata gateway below. This is a protocol endpoint for an MCP client, not a normal web page.

• Connection name: Alkemata
• Transport: Streamable HTTP (remote)
• Server URL: https://alkemata.com/wp-json/mcp/alkemata-public
• Public reading and pending proposals: no authentication or API key.

In your client’s MCP or custom connector settings, add the URL exactly as shown, save, and enable the Alkemata tools. A client that supports only a local stdio process cannot connect directly to this URL. Start by asking the assistant to call get_agent_guidance, search a published article, and return its canonical Alkemata link. The public MCP tutorial gives a short example.

Use private project tools or publish a notebook

For private actions, choose OAuth / browser sign-in in the client and sign in with your own Alkemata account. The client requests an access token from Alkemata Keycloak; never enter your Alkemata password as an MCP server secret or share a token with another user. Access also depends on your project role or publishing permission.

• Read OpenProject work packages and wiki pages: request projects:read.
• Create or edit OpenProject work packages and wiki pages: request projects:read projects:write.
• Upload a notebook or create map content: request knowledge:contribute.

The standard sign-in scopes are openid profile email. Request only the additional scope needed for your task. Public article, map and notebook reading needs no token. Project tools also check your OpenProject project membership and permissions.

OAuth parameters for clients that ask for them

• Issuer / authorization server: https://auth.alkemata.com/realms/alkemata
• Authorization URL: https://auth.alkemata.com/realms/alkemata/protocol/openid-connect/auth
• Token URL: https://auth.alkemata.com/realms/alkemata/protocol/openid-connect/token
• OAuth flow: authorization code with PKCE (S256).
• Protected resource metadata: https://alkemata.com/.well-known/oauth-protected-resource/wp-json/mcp/alkemata-public
• Client ID and, if applicable, client secret: specific to your MCP client registration; there is no shared value to copy from this page.
• Redirect / callback URI: use the exact URI supplied by your MCP client when registering it. Do not invent a callback address.

ChatGPT custom connectors can use the Alkemata Keycloak registration flow. For another client that cannot register automatically, ask an Alkemata administrator to register its client ID and exact callback URI and enable the requested optional scopes. The site’s separate WordPress administration MCP has different OAuth settings; use the gateway URL above for Alkemata knowledge, notebooks and projects.

Check the connection

1. Call get_agent_guidance and search a published article to verify the public connection.
2. For OpenProject, authorize projects:read and call openproject_list_projects. If your project is missing, check both the OAuth scope and your project membership.
3. For a requested edit, authorize projects:write, then read the current item before updating it. For notebook upload, authorize knowledge:contribute and use the returned notebook URL.

If sign-in returns to “Reconnect,” check the exact gateway URL, your client’s callback URI and the scopes assigned to its OAuth registration. The path-specific protected resource metadata above is for this gateway; the metadata at the website root describes a separate WordPress administration service. For tool details and examples, see Alkemata MCP: Articles, Notebooks and Projects.