Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.chatgrid.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Step 1: Get an API key

Go to chatgrid.ai/settings/api-keys and create a new key. It starts with cgk_live_.

​
Step 2: Add to your project’s .mcp.json

Create or edit .mcp.json in your project root:
.mcp.json
{
  "chatgrid": {
    "command": "npx",
    "args": ["chatgrid-mcp"],
    "env": {
      "CHATGRID_API_KEY": "cgk_live_your_key_here"
    }
  }
}
Add .mcp.json to your .gitignore if it contains your API key directly. Or use an environment variable reference instead.

​
Step 3: Restart Claude Code

Close and reopen Claude Code (or run /mcp to reload). You should see chatgrid listed as a connected MCP server.

​
Step 4: Try it

Talk to Claude Code naturally. It will use ChatGrid tools automatically.

​
Create a board

> Create a ChatGrid board for the payments project

​
Add a YouTube video

> Add this YouTube video to the payments board: https://youtube.com/watch?v=abc123
The video appears on the canvas with its thumbnail. The transcript is extracted and vectorized automatically — you can search and ask questions about the video content.

​
Add a website

> Add this blog post to the board: https://vercel.com/blog/ai-sdk-4-2
The page is scraped, and the content is chunked and vectorized. The node shows the site’s favicon and domain.

​
Upload a PDF

> Upload this PDF to the board: /Users/me/docs/architecture.pdf
The file is uploaded to storage and a PDF node appears on the canvas. Text is extracted and vectorized for search.

​
Upload an image

> Upload this diagram to the board: /Users/me/docs/system-diagram.png

​
Add a text note

> Add these architecture notes to the board: "We use Stripe webhooks
  verified with the signing secret. Events go through Inngest for
  reliable processing. See src/server/stripe/webhooks.ts."
Notes appear as sticky notes on the canvas with the text visible.

​
Search your knowledge

> Search the payments board for webhook verification

​
Ask questions

> Based on our team's board, how should I implement retry logic
  for failed payment webhooks?
Claude Code will search your board, find relevant sources, and give you an answer grounded in your team’s actual knowledge.

​
All MCP tools

ToolWhat it does
list_boardsSee all your team’s boards
create_boardStart a new project board
list_nodesSee everything on a board
add_resourceAdd a YouTube video, website URL, or text document
add_noteAdd a sticky note with text content
upload_fileUpload a PDF, image, or document file from disk
search_boardSemantic search across all board content
ask_boardAsk AI a question answered by board content

​
Supported content types

TypeHow to addWhat happens on the canvas
YouTubePaste a YouTube URLVideo thumbnail, title, transcript extracted and vectorized
WebsitePaste any URLPage scraped with favicon, content vectorized
PDFUpload from diskPDF viewer node, text extracted and vectorized
ImageUpload from diskImage displayed on canvas
TextType or paste contentSticky note with visible text, vectorized

​
Tips

Keep boards focused. A “Payments” board, a “Frontend” board, an “Infrastructure” board. Don’t dump everything in one board.
Found a useful Stack Overflow answer? Tell Claude Code to add it to the board. Read a good blog post? Add it. Watching a YouTube tutorial? Add that too. The board gets smarter over time.
The MCP server can read files from your local disk. Just give it the path: “Upload /path/to/file.pdf to the board”. No need to host files anywhere.
Everyone on the team can use the same API key (or their own). The board is shared. One dev adds a doc, everyone benefits.