Teak for AI Agents

Connect AI agents to Teak with MCP, ChatGPT connectors, REST, CLI, and llms.txt

Teak gives AI agents a private memory layer for saved links, notes, files, tags, and design references. Agents can use the hosted MCP server at https://teakvault.com/mcp, the REST API at https://teakvault.com/api/v1, or the command-line app, with browser OAuth or teakapi_ API keys for authentication.

When to use Teak

Use Teak when a person wants to keep knowledge beyond the current conversation: save a link or note, retrieve something they collected earlier, organize research with tags, or sync the same private library across apps and agents. Use the MCP server for assistant workflows, the REST API for an integration, and the CLI for local scripts. Do not use Teak as a temporary scratchpad when the information does not need to persist.

What can agents do with Teak?

Agents can save, search, read, update, favorite, delete, and sync cards through identical operations on the MCP server and the REST API.

How do I connect Claude?

claude mcp add --transport http teak https://teakvault.com/mcp

Start the MCP connection in Claude and complete browser sign-in when prompted. API keys also work for clients that let you set an Authorization: Bearer <token> header.

Setup for Codex, Cursor, VS Code, and ChatGPT is in Connect your client.

How do I connect ChatGPT or Deep Research?

Use https://teakvault.com/mcp as the remote MCP server URL. Teak exposes the plain search and fetch tools ChatGPT connectors expect — see MCP for the tool contracts.

How do I use the REST API?

Use the production base URL https://teakvault.com/api/v1. See the API docs for the full base URL list, authentication, endpoints, and error format — that page is the source of truth for the REST contract.

What should coding agents read first?

• https://teakvault.com/llms.txt for the compact documentation map
• https://teakvault.com/llms-full.txt for the full docs context
• https://teakvault.com/docs/api.md for the REST API contract
• https://teakvault.com/reference for the interactive OpenAPI reference
• https://teakvault.com/docs/mcp.md for MCP setup and tools
• https://teakvault.com/docs/webmcp.md for in-browser WebMCP tools
• https://teakvault.com/.well-known/mcp.json for remote MCP discovery metadata
• https://teakvault.com/agent-readability.json for the machine-readable docs surface map
• https://teakvault.com/.well-known/agent-skills/index.json for the Teak Agent Skill

Can agents use the command line?

Yes. Install the Teak CLI and sign in:

npx teak-cli@latest login

Then use commands such as:

teak search design
teak add https://teakvault.com
teak tags

Can agents use Teak inside the browser?

Yes. In browsers that ship the draft WebMCP API, the signed-in Teak web app registers read-only teak_search_cards and teak_get_card tools plus a declarative search form, all running in your existing session with no extra authentication. See WebMCP for requirements and the tool reference.

Is there an Agent Skill?

Yes. Teak ships a public Agent Skill for assistants that support skills-based workflows. Use it when an agent needs to save, search, retrieve, update, favorite, delete, or sync Teak cards through the CLI, API, SDK, or MCP server.

Install it from Skills.sh:

npx skills add praveenjuge/teak --skill teak

Works with Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, and other skills-compatible agents. Agents that discover skills from websites can also find it at https://teakvault.com/.well-known/agent-skills/index.json. The skill covers when to use CLI vs API vs MCP vs SDK, browser sign-in or API key auth, and never printing, persisting, or committing secrets.