# spinach.ai for AI agents. Managed auth, ready-made tools.

> Find past meetings and read their summaries, action items and transcripts in spinach.ai on behalf of each of your users.

- Page: https://www.agent200.com/connectors/spinach-ai/
- Category: Developer tools
- Authentication: Managed OAuth
- Identifier in code: `spinach_ai`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-18

## Instructions for AI agents

Connector: spinach.ai, through Agent200. In code: "spinach_ai".
What it does: Find past meetings and read their summaries, action items and transcripts in spinach.ai on behalf of each of your users.
Page: https://www.agent200.com/connectors/spinach-ai/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on spinach.ai's own page, through the authorization link Agent200 returns. Never ask a user for a spinach.ai password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: spinach_ai_list_meetings, spinach_ai_get_summary, spinach_ai_get_action_items, spinach_ai_get_transcript. Name "spinach_ai" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/spinach-ai/framework/claude/
   https://www.agent200.com/connectors/spinach-ai/framework/chatgpt/
   https://www.agent200.com/connectors/spinach-ai/framework/claude-code/
   https://www.agent200.com/connectors/spinach-ai/framework/muse/
   https://www.agent200.com/connectors/spinach-ai/framework/grok-bot/
   https://www.agent200.com/connectors/spinach-ai/framework/openai-dots/
   https://www.agent200.com/connectors/spinach-ai/framework/claude-duet/
   https://www.agent200.com/connectors/spinach-ai/framework/hermes-agent/
   https://www.agent200.com/connectors/spinach-ai/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the spinach.ai connector, your agent works with each user's own spinach.ai meeting notes. It can list past meetings and read a meeting's summary, action items and transcript, using only the tools your project allows.

spinach.ai is an AI meeting assistant that takes notes and action items in video calls.

## spinach.ai tools

- **List meetings** (`spinach_ai_list_meetings`, read): List the user's recorded meetings.
- **Get a summary** (`spinach_ai_get_summary`, read): Read the summary of a meeting.
- **Get action items** (`spinach_ai_get_action_items`, read): Read the action items from a meeting.
- **Get a transcript** (`spinach_ai_get_transcript`, read): Read the transcript of a meeting.

## Limits you can set

**Turn single tools on or off.** Let the agent read summaries and action items, and switch off `spinach_ai_get_transcript` so it never reads full transcripts.

**Restrict what the agent reaches.** Choose the endpoints a project may use, for example summaries but not transcripts. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect spinach.ai

Each end user authorizes their own spinach.ai account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own spinach.ai account, once.
const connection = await agent200
  .user("user_123")
  .connect("spinach_ai");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the spinach.ai tools

Name the user, the model and the tools. The model decides which spinach.ai tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "What were the action items from this morning's standup",
    tools: ["spinach_ai"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, connecting their own spinach.ai account. Each connection belongs to that user.

**What access is requested.** Access to the meeting notes the connection needs, such as summaries, action items and transcripts. Users can revoke it later from their spinach.ai account settings.

## Example requests

- "What were the action items from this morning's standup"
- "Summarize my call with the Acme team yesterday"
- "Find what we decided about pricing in last week's meetings"

## Guides: spinach.ai with your AI framework

- [spinach.ai + Claude](https://www.agent200.com/connectors/spinach-ai/framework/claude.md): Connect spinach.ai to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [spinach.ai + ChatGPT](https://www.agent200.com/connectors/spinach-ai/framework/chatgpt.md): Give ChatGPT access to spinach.ai through Agent200: managed OAuth, ready-made tools and one API key.
- [spinach.ai + Claude Code](https://www.agent200.com/connectors/spinach-ai/framework/claude-code.md): Have Claude Code build a spinach.ai agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [spinach.ai + Muse](https://www.agent200.com/connectors/spinach-ai/framework/muse.md): Connect spinach.ai to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [spinach.ai + Grok Bot](https://www.agent200.com/connectors/spinach-ai/framework/grok-bot.md): Connect spinach.ai to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [spinach.ai + OpenAI Dots](https://www.agent200.com/connectors/spinach-ai/framework/openai-dots.md): Give OpenAI Dots access to spinach.ai through Agent200: managed OAuth, ready-made tools and one API key.
- [spinach.ai + Claude Duet](https://www.agent200.com/connectors/spinach-ai/framework/claude-duet.md): Connect spinach.ai to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [spinach.ai + Hermes Agent](https://www.agent200.com/connectors/spinach-ai/framework/hermes-agent.md): Connect spinach.ai to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [spinach.ai + OpenClaw](https://www.agent200.com/connectors/spinach-ai/framework/openclaw.md): Connect spinach.ai to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the spinach.ai OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for spinach.ai.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's spinach.ai connection, never another user's. It cannot reach anything the user or spinach.ai has not authorized.

### Can I limit what my agent can do in spinach.ai?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [GitHub](https://www.agent200.com/connectors/github.md): Read repositories and work with issues and pull requests as the connected user.
- [GitLab](https://www.agent200.com/connectors/gitlab.md): Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.
- [Bitbucket](https://www.agent200.com/connectors/bitbucket.md): List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.
- [Jira](https://www.agent200.com/connectors/jira.md): Search, create and transition Jira issues for the connected user.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
