# Connection Overview

## Choose a connection

| Use case | Recommended path |
| --- | --- |
| Hosted AI app such as ChatGPT, Grok, or Claude | MCP with OAuth |
| IDE or coding agent | MCP with a Memside API key |
| JavaScript application | JavaScript SDK |
| Python application | Python SDK |
| Another language or script | REST API |
| Chat inside the Memside app | Bring an AI provider |

## Connection details

| Setting | Value |
| --- | --- |
| MCP server | `https://api.memside.com/mcp/` |
| REST API | `https://api.memside.com` |
| API-key header | `Authorization: Bearer mem_sk_example_key` |

Create and revoke API keys under **Settings > Developer & API**.

:::caution
Treat an API key like a password. Do not put it in a URL, commit it to source
control, or include it in a screenshot or shared message.
:::

## Hosted AI apps

- [ChatGPT](/connect/chatgpt/)
- [Grok](/connect/grok/)
- [Claude](/connect/claude/)

These setup paths use OAuth when supported. OAuth allows sign-in without
pasting an API key into the AI app.

## IDEs and coding agents

- [VS Code](/connect/vscode/)
- [GitHub Copilot](/connect/github-copilot/)
- [Cursor](/connect/cursor/)
- [Codex](/connect/codex/)
- [Google Antigravity](/connect/antigravity/)
- [Claude Code](/connect/claude-code/)
- [OpenCode](/connect/opencode/)

These tools commonly use a Memside API key in a bearer header. Authentication
options can vary by app version.

## In-App Assistant

The Memside in-app assistant uses a provider configured under **Settings > LLM
Configuration**.

See [In-App Assistant](/connect/in-app-assistant/).

## Applications and SDKs

- [Developer quickstart](/developers/)
- [JavaScript SDK](/developers/javascript-sdk/)
- [Python SDK](/developers/python-sdk/)
- [REST API](/developers/api-reference/)

## What connected AI tools can do

Available actions can include:

- search and read Memories;
- create or update Memories;
- save and continue from checkpoints;
- use Tasks, Subjects, Connections, Profile, Rules, and Skills;
- suggest Facts for review.
- search public Library Templates;
- review owned Template status and bounded draft content;
- create, update, review, publish, unpublish, or republish owned Templates.

Two independent settings control whether MCP exposes Memory tools, Library
tools, or both. Library creator actions require a Library creator account and
follow the same ownership and review requirements as the Library website.

Secret Memories remain inside the Memside app. Fact suggestions require review.
Permanent deletion requires AI delete permission and explicit confirmation.

## Test a connection

Start with a read-only request:

```text
Use Memside to find the Weekend trip plan Memory and summarize the next step.
```

Test create, update, and delete actions only after reads work.

For Library discovery, a simple read test is:

```text
Search the Memside Library for a weekly planning Template.
```

## Troubleshooting

See [Troubleshooting](/help/troubleshooting/) for authentication, missing tools,
and client-specific issues.

See [Library access through MCP and API](/library/mcp-and-api/) for the connected
Template workflow.