Docs
Get API keys
Docs / MCP

Konecto MCP server

Let Claude, ChatGPT and other MCP clients operate Konecto for an organiser.

The Konecto MCP server lets an AI assistant act for a signed-in organiser. It is a remote server using Streamable HTTP with OAuth 2.1.

Server URL: https://mcp.konec.to/mcp
Transport:  Streamable HTTP (stateless, JSON responses)
Auth:       OAuth 2.1 with PKCE (S256), dynamic client registration
Metadata:   https://mcp.konec.to/.well-known/oauth-protected-resource
            https://api.konec.to/.well-known/oauth-authorization-server

Connect

  • Claude: Settings → Connectors → add custom connector → paste the server URL → sign in.
  • ChatGPT: add the Konecto app, or add a connector with the server URL where your plan allows it → sign in.
  • Other clients: any client that supports remote MCP servers with OAuth.

During sign-in the organiser chooses the organisation and the scopes to grant. Access tokens last an hour and refresh silently for 30 days; disconnect any time from Settings, Connected apps in the organiser app (the next tool call then fails with 401).

Principles

  • Every tool maps to the Admin API; the MCP server has no business logic of its own.
  • Tools return structured JSON, a short summary and a link to the matching organiser-app page.
  • Money-moving or irreversible actions return a confirmation link the organiser completes. The assistant never pays.
  • Tools for modules that are not enabled return module_required with the price and an enable_module link.
  • Every call is written to the organisation's audit log with the tool name.
  • Two resources ship with the server: konecto://docs/agent-guide (the rules an assistant follows) and konecto://events/{id} (an event summary).
PreviousCore concepts

Plain-text version for agents: llm.konec.to/docs/mcp/overview.md