← Home

Connect what
you know.

Start with built-in Thegram AI, or connect the AI you already use. Choose your knowledge sources and build a system for yourself or your team.

External connections require setup. Source availability depends on workspace configuration and provider authorization. Connecting a source is not permission to copy everything.

01 / Knowledge sources

02 / Your AI & developer routes

Notion

Knowledge source / Setup required

Your notes.
In context.

Make selected pages part of your knowledge system. Keep the connection and the decision to save separate.

If the connector is not available in your workspace, stop and ask your administrator. This page does not connect an account or import data.

  1. Choose the intended account

    Open Thegram’s connections and select Notion. Availability depends on your workspace configuration.

  2. Review the page access

    Use Notion’s authorization flow and review the pages you make available. Follow any workspace restrictions.

  3. Decide what to keep

    Use the relevant source in a project. Connecting a source does not authorize importing every page.

Google Drive™

Knowledge source / Setup required

Your files.
Your choice.

Connect Drive explicitly. Signing in with Google is not the same as granting access to your files.

If the connector is not available in your workspace, stop and ask your administrator. This page does not connect an account or import data.

  1. Connect Drive separately

    Choose the intended Google account. Personal Drive and a company Shared Drive are different destinations.

  2. Choose the files you allow

    The documented drive.file route covers files the app created or that you explicitly opened with it, not unrestricted browsing.

  3. Check the destination and access

    Review the returned mount and permissions. Do not copy a denied document into another destination to bypass access.

Slack

Knowledge source / Setup required

Conversations.
With context.

Bring relevant conversations into project knowledge without treating workspace access as blanket permission to retain everything.

If the connector is not available in your workspace, stop and ask your administrator. This page does not connect an account or import data.

  1. Choose the Slack workspace

    In Thegram’s connections, choose Slack and use your intended workspace. An administrator may need to enable it.

  2. Review the requested scopes

    Check what the authorization covers and respect your workspace’s conversation and data policies.

  3. Keep the relevant knowledge

    Choose the context worth saving and preserve its source. Authorization and durable capture are separate decisions.

GitHub

Knowledge source / Setup required

Project work.
Remembered.

Use repository and issue context alongside the decisions that explain your work.

If the connector is not available in your workspace, stop and ask your administrator. This page does not connect an account or import data.

  1. Connect the right account

    Choose GitHub in Thegram’s connections. Use the account associated with the intended project.

  2. Review repository coverage

    Check the access requested and your organization’s restrictions. A listed connector is not proof it is enabled in every workspace.

  3. Keep decisions with their sources

    Bring relevant project context into knowledge you intend to retain. Review the source and destination before saving.

Linear

Knowledge source / Setup required

Project context.
Not another silo.

Keep the useful context around project work connected to your knowledge and AI.

If the connector is not available in your workspace, stop and ask your administrator. This page does not connect an account or import data.

  1. Choose your Linear workspace

    Select Linear from Thegram’s connections. The workspace must have the integration configured.

  2. Review the authorization

    Use the provider’s normal flow. Check the account, workspace and requested access before approving.

  3. Use context deliberately

    Work with relevant project information and preserve its source. Do not imply automatic capture of every issue.

Thegram AI

Built-in AI / Included in Thegram

Your knowledge.
Your Thegram AI.

Included in Thegram. Work with your conversations and the authorized documents in your selected space, without connecting an external AI account.

Thegram AI is part of Thegram, not another provider connection. No external AI account is required.

  1. Choose Thegram AI

    Open Thegram and select Thegram AI from the app switcher. Sign in with your intended Thegram account if needed.

  2. Choose the right space

    Use your personal space or the intended team workspace. Thegram AI uses only the conversation and documents you are allowed to access in that space.

  3. Start with your knowledge

    Ask about your project, then review the sources behind the answer. Usage allowances and workspace permissions still apply.

OpenAI

AI apps & coding / Setup required

Thegram.
In ChatGPT.

ChatGPT uses the Thegram plugin and OAuth. Codex has a separate coding-agent plugin and scoped-key route.

Follow the current host and Thegram setup screens. This page does not install a plugin, issue a key or authorize access.

  1. Install the Thegram plugin

    Open the published ChatGPT setup page and use the host’s normal installation flow. No Thegram API key goes into chat.

  2. Sign in and review access

    Use your intended Thegram account and authorize only the resources you want ChatGPT to use.

  3. Start with a read

    In a new conversation, ask what Thegram remembers about your projects. A connected tool is not permission to save new information.

Anthropic

AI apps & coding / Setup required

Thegram.
In Claude.

Install the memory skill and connect the MCP tools. One does not prove the other is installed or authorized.

Follow the current host and Thegram setup screens. This page does not install a plugin, issue a key or authorize access.

  1. Install the current Claude plugin

    Use Claude’s plugin upload/install flow with the current package from Thegram’s setup page. The package includes the memory skill.

  2. Connect Thegram with OAuth

    Use Connectors. If adding it manually, use https://vault.thegram.one/mcp, then sign in and review the intended access.

  3. Check in a new conversation

    Ask: “What does Thegram remember about my projects?” Read-only access cannot save. Google Drive authorization is separate.

xAI

AI app / Setup required

Thegram.
In Grok.

Grok uses a custom MCP connector and OAuth. The xAI backend API route is separate.

Follow the current host and Thegram setup screens. This page does not install a plugin, issue a key or authorize access.

  1. Add a custom connector

    Use Grok’s Connectors screen. Enter Thegram and https://vault.thegram.one/mcp. Business and Enterprise may need an administrator first.

  2. Follow the published OAuth setup

    Use the public client identity and endpoint settings from the detailed setup guide. Do not use an API key as the OAuth client ID.

  3. Review resource permissions

    Connect with your own Thegram account. Allow only the vaults or separately authorized Drive accounts Grok needs.

Cloudflare

Build your own agent / Setup required

Your agent.
Shared knowledge.

Use a remote MCP client from Cloudflare’s Agents SDK. This is a developer route, not a consumer chat-app login.

Follow the current host and Thegram setup screens. This page does not install a plugin, issue a key or authorize access.

  1. Issue a scoped Thegram key

    Create a separate key for the agent. Choose only the intended resources and start with read access.

  2. Keep it in a server-side secret

    Store the key as a Worker secret, not in source code, frontend storage or a conversation.

  3. Connect and verify with a read

    Use the published Agents SDK example. A portal can share one bearer key across admitted users, so keep its scope narrow.

For yourself

One project.
Knowledge that stays.

Start with a project you care about. Choose Thegram AI or connect one AI, then a source you control. Ask it to read what is already there. Save a decision only when you choose to, then inspect the saved revision in Thegram.

Start with one project ↗

For your team

Shared context.
Deliberate access.

Choose a shared project and a person responsible for its knowledge. Review source permissions, destination access and which people or agents can write. Keep personal and company resources separate.

Plan access first ↗

More ways to connect.

Coding agents ↗Muse ↗dots ↗API services ↗Google CC — coming soon

Product names and logos identify the relevant services, not an endorsement or partnership. Logo sources ↗