Integration

Keystatic integration

Keystatic is a Git-based content management system that stores content as files in your repository. It uses the GitHub API under the hood for reading and writing content. These endpoints represent the GitHub Contents API operations that Keystatic relies on for managing collections, singletons, and media files in a repository.

Connect Keystatic How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Keystatic.Built from the 5 Keystatic tools below, on the connection you add once.

Common Keystatic use cases

Delete blog post
Save new blog post
Read blog post content
Get current branch HEAD
List all collection entries
List collection entries
Remove collection entry
Update collection entry
Resolve branch to commit
Browse repository structure

What you can do with Keystatic

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Content, 3 operations

create_or_update_fileCreate or update filePUTCreate or update a file in the repository
delete_fileDelete fileDELETEDelete a file from the repository
get_contentGet contentGETGet file or directory contents from the repository

Reference, 1 operation

get_refGet refGETGet a Git reference (branch or tag)

Tree, 1 operation

get_treeGet treeGETGet a Git tree with all files and directories

Keystatic API rate limits

5,000 requests per hour

GitHub API rate limits apply. Authenticated requests: 5000/hour.

These are the limits Keystatic documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Keystatic documentation for current values.

Use Keystatic from Claude Code, Cursor or Codex

Connect Keystatic in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Keystatic operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Keystatic

Create your workspace
Sign up free. Nothing to install.
Connect Keystatic once
Add your Keystatic connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Keystatic integration FAQ

What can you do with the Keystatic integration?

LiveContext exposes 5 operations on Keystatic, covering content, reference and tree. Common uses include Delete blog post, Save new blog post and Read blog post content.

What are the Keystatic API rate limits?

Keystatic documents 5,000 requests per hour. GitHub API rate limits apply. Authenticated requests: 5000/hour. Limits are set by Keystatic and can depend on your plan.