Integrations › GitHub

Dev Platform

Your Repos Inform Every AI Tool

Issues, PRs, and repo context become memory your AI can query anywhere.

Get API Key →
12MCP tools
0.01mslookup
Freefor individuals
ed25519signed

The Problem

Your GitHub repos hold critical context — architecture decisions in PRs, bug context in issues, dependency choices in commits. But none of your AI tools can access it. You end up re-explaining the same context to Cursor, Claude Code, and ChatGPT.

PR decisions become queryable context.

• • • GitHub PR #42
Decision: Use Supabase for auth
Reviewed by @sarah, merged
✓ Ingested · rct_pr42 · source: github
• • • Claude Code
> What auth system should I use?
✦ From GitHub PR #42, merged 2 days ago
Supabase for auth — decided in PR #42
Receipt: rct_pr42 · source: github
Step 1
Connect
→
Step 2
Ingest + Extract
→
Step 3
Verify + Receipt

The Fix

Connect GitHub1-click OAuth · read-only

Connect via API:

bash
# Add MCP server to your AI tool: # URL: https://mcp.verifiedstate.ai/mcp # Header: Authorization: Bearer YOUR_API_KEY # Then: memory_ingest with source_type "github" # Your repo decisions become queryable across tools # Or ingest directly: curl -X POST https://api.verifiedstate.ai/ingest \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"namespace_id":"your-ns","content":"PR #42: chose Supabase for auth","source_type":"github"}'

What You Get Back

✓ VERIFIED
receipt.json
{ "receipt_id": "rct_7f3a...", "assertion": "User prefers dark mode", "status": "verified", "confidence": 0.94, "signature": "ed25519:a8c3f1...", "verified_at": "2026-04-06T14:32:01Z", "chain_position": 42 }

Without VerifiedState vs. With VerifiedState

FeatureWithoutWith VerifiedState
PR decisions Buried in review comments Trusted State every tool can query
Issue context Re-read the thread each time Ingested once, available everywhere
Architecture choices Lost in commit messages Queryable with proof and timestamps
Cross-tool GitHub-only context Cursor, Claude Code, Obsidian all know

FAQ

Does this require a GitHub App?

No. Click Connect GitHub above and authorize with OAuth. Your repos, PRs, and issues become queryable memory across all your AI tools.

Can I query PR decisions from Cursor?

Yes. Once connected, any MCP-connected tool can query those decisions as Trusted State.

What permissions does it need?

read:user (your profile) and repo (to read issues, PRs, and code context). We never write to your repos.

Related Integrations

Never explain your project twice.

Add VerifiedState once. Keep project state available across your AI agents.