![\"Connany](\"public/brand/logo.svg\"){kind=logo}
Connect agents to your users’ tools, accounts, and workspaces.
\n\n\nConnany is an open-source, multi-tenant connector service for agent applications. It manages user authorization, connections, and credentials so your agent backend can list tools and work with authorized data through a REST API or TypeScript SDK, without handling provider tokens.\n\nIt ships with 25 connectors across collaboration, development, databases, analytics, payments and design. Every connector except GitHub uses the provider's official hosted MCP server and is enabled with one click: Connany registers the OAuth client automatically. Two ways in: agent products integrate through a REST API and TypeScript SDK, and individuals add Connany to Claude Code, Codex or Cursor as an MCP server (with an agent skill) to use the connectors with their own accounts.\n\n\n\n## Features\n\n- **Admin console:** configure connectors once and sync their tool catalogs, create a project for each agent, manage each project's API keys (zero-downtime rotation), inspect user connections and activity, read the API docs and agent integration guide, and (as an administrator) manage console users as administrators or members.\n- **User authorization:** hosted OAuth pages, single-use state, browser binding, and PKCE (S256) on every OAuth flow.\n- **Project isolation:** every API key belongs to a project; user data is scoped to `project_id + external_user_id`.\n- **Connection management:** multiple accounts and workspaces, listing, active checks, reconnection, disconnection, and upstream revocation retries.\n- **Tool listing and calls:** list the official MCP tools a user's connection can use with `GET /v1/connections/{id}/tools` (or browse each connector's catalog with `GET /v1/tools`), inspect parameter schemas and read/write metadata, and call them with `POST /v1/connections/{id}/tools/{name}/call`. The SDK can expose just two tools to a model: `list_tools` and `call_tool`.\n- **MCP server and skill:** Connany is itself a remote MCP server with OAuth 2.1 sign-in (dynamic client registration, PKCE). Users add it once to Claude Code, Codex or Cursor, connect accounts from the conversation, and call tools through a few meta-tools; reads and writes are separate tools so clients can confirm every change. A downloadable skill teaches the agent the workflow.\n- **Event feed:** one project-wide feed (`GET /v1/events`) reports connections, reauthorization needs, disconnections, and tool calls for every user.\n- **Credential protection:** AES-256-GCM encryption for connector and user credentials, hashed API keys, and database transaction locks to coordinate token refresh and execution.\n\n## Quick start\n\nRequires Node.js 22+, npm, and PostgreSQL 15+. The following uses Docker to start a local database:\n\n```bash\ngit clone git@github.com:thinkany-ai/connany.git\ncd connany\nnpm ci\nnpm run setup\ndocker compose up -d postgres\nnpm run db:migrate\nnpm run admin:create -- admin@example.com\nnpm run dev # or: make dev\n```\n\nEnter an administrator password of at least 8 characters when prompted. `npm run setup` creates `.env` with a random encryption key without overwriting an existing file. The root `compose.yaml` starts only PostgreSQL; its default password is for local development.\n\n- Admin console: