Short answer
Can cMCP link to Jira, GitHub, e-mail and more?
Yes, sixteen kinds of source are built (stage 1v, 2026-10-11; Linear and Notion 2026-10-12): Jira, Confluence, GitHub, GitLab, Bitbucket, Linear, Notion, Slack, Microsoft Teams channels, Microsoft 365 mail, Gmail, IMAP mailboxes, OneDrive / SharePoint, Google Drive, meeting transcripts (Teams, Zoom, Google Meet) and database views (PostgreSQL, MySQL / MariaDB, SQL Server). Jira ran against the real service; every other type is proven end to end against a test double of the vendor's API or real test databases, not yet against a real vendor account.
Everything that flows in follows the same rules: read-only, each mailbox, channel, drive, repository, space or meeting organiser becomes a space that is read only once it is linked to a project or team (or one fixed target: a project, a client or your own memory), proposed facts wait for a person's approval, secrets sit encrypted in the secret store, and the web-admin or an account admin switches each type on (all new types start off).
The full list
| Link | Status | What it does | Rules and limits |
|---|---|---|---|
| Jira Cloud | Built | Issues and comments of chosen projects become proposed facts. The project lead approves each one before it becomes memory. | On by default; an account admin can switch the type off. Read-only. A client connection also needs the client lead. Proven against the real Jira Cloud. |
| Confluence Cloud | Built · test double | Pages and comments of chosen spaces. | Pages with view restrictions (also inherited) are never read. Atlassian site allow-list. |
| GitHub | Built · test double | The repository list, issues, pull requests, discussions and Markdown docs (README, docs/, ADRs). | Fine-grained read-only token only; members' items only; code is never read. |
| GitLab | Built · test double | Issues, merge requests and their comments of chosen projects or a group (gitlab.com or an allow-listed server). | Read-only token only; confidential issues, internal and system notes skipped. |
| Bitbucket Cloud | Built · test double | Pull requests, issues and their comments in a workspace. | Private repositories only; inline code comments skipped. |
| Linear | Built · test double | Issues and their comments in chosen teams. | Personal API key with Read only; guests', bots' and integrations' text and archived issues never read. |
| Notion | Built · test double | Pages under chosen top pages or databases (sub-pages and database rows included). | Internal integration with Read content only; only pages shared with it and under the chosen ones; comments, files, images and code never read. |
| Slack | Built · test double | Messages and thread replies in chosen channels. | Bot token of an app made only for your workspace; other workspaces' guests, bots and direct messages never read. |
| Microsoft Teams channels | Built · test double | Messages and replies in chosen channels. | Guests, external users and app posts skipped; needs Microsoft's protected-API approval for channel messages. |
| Microsoft 365 mail | Built · test double | Shared mailboxes (or a person's own, through the organization's app). | No attachments; bot and no-reply mail skipped; approved one by one. |
| Gmail | Built · test double | Workspace mailboxes (or a person's own, through the organization's service account). | High-risk switch; only mail Google itself verified from listed sender domains; approved one by one. |
| Mailbox (IMAP) | Built | Chosen folders, only mail from listed sender domains the mail server verified (DKIM / DMARC). Text only, no attachments. | Off by default; mail is approved one by one, never in bulk. Password-based IMAP servers on the allow-list. |
| OneDrive / SharePoint, Google Drive | Built · test double | Text, Markdown, CSV, Word, PowerPoint, Excel and Google Docs / Sheets / Slides in chosen drives or folders. | Other files, images and anything over 5 MB never read; downloads never get the token. |
| Meeting transcripts (Teams, Zoom, Google Meet) | Built · test double | Transcripts of meetings the listed people organised. | High-risk switch; never recordings; private-marked meetings and meetings with outside people skipped; facts restricted and approved one by one; text removed after 30–90 days. |
| Database views (PostgreSQL, MySQL / MariaDB, SQL Server) | Built · test databases | Named read-only views become proposed facts (rows as text). | Views only; a login that can only read (checked); 500 rows a run; allow-listed hosts; SQL Server has no read-only transaction (rights check and rollback instead). |
| Personal connections | Built | A person's own mailbox, drive, meetings or tool account, feeding only their own User memory. | Microsoft 365, Gmail and meetings use an organization connection the ADMIN offered: the person enters no secret and reads only their own address. |
| Git repository addresses | Built | A repository address (the git remote) is mapped to a project. Claude Code sends the remote of the folder it works in, and cMCP gives it that project's memory. | Only the address is used for this mapping. Issues and pull requests come through the GitHub / GitLab / Bitbucket connectors above; code is never read. |
| Jira project keys | Built | A Jira key is mapped to a project or team, so imported facts land in the right place. | Org admins or the place's lead. |
| AI apps (MCP and REST) | Built | Claude Code, any MCP app that can sign in with OAuth and a client ID, and bots with their own login. They read memory, save facts, ask for changes. | See How an AI app connects. Claude on the web or phone: not supported yet. |
| Company login (Keycloak) | Built | Password plus a one-time code (authenticator app) for real people. | Single sign-on with Google or Microsoft accounts is not set up. |
| E-mail out | Built | Reminders (counts and a link), once a day, to verified addresses. | Company domains only for the pilot account. Phase 2 accounts send with their own mailbox. |
| Resource catalogue | Built | A list of where things live (repositories, databases, folders, links) that AI apps can look up. Locations only, never passwords. | It records places; it does not connect to them. |
| Webhooks (push instead of polling) | Phase 2 | Faster updates from Jira and others. | Today connectors poll every 15 minutes or more. |
| Writing into outside systems | By design: no | cMCP never creates Jira issues, sends mail for you, edits repositories or changes databases. | Every link is read-only. This keeps a poisoned note from acting in the outside world. |
| Calendars, CRM, ticket systems | Not chosen yet | Offered as further connectors; not part of stage 1v. | Each would use the same catalogue, rules and tests. |
How a link gets set up
- Type onThe web-admin (Connectors card) or an account admin switches the type on; Gmail and meetings are high-risk switches.
- Vendor set-upEach type lists what to create at the vendor first (an app registration, a service account, a read-only token).
- Host allowedA super-user adds the server to the allow-list (databases, mail, a self-managed GitLab).
- Org admin adds itConnectors screen: type, target, settings and the password or token (write-only).
- Spaces linkedEach mailbox, channel, drive, repository or space found is linked to a project or team; unlinked ones are not read.
- Client lead approvesOnly for a client's memory, by a lead other than the person who set it up.
- Runs on scheduleFacts are proposed, never saved directly.
- Lead approves factsApprovals screen, one by one for mail; a covering colleague can decide for a lead.