Cookbooks
Which runnable recipe gives an agent built on LangChain, OpenAI Agents, Anthropic, Vercel AI SDK or Google ADK nima's MCP tools, with a plain HTTP fallback?
The nima cookbooks are runnable recipes that give an agent built on a popular framework access to nima's tools. Each recipe connects to the same MCP server, https://mcp.getnima.io/mcp, with a personal API key sent as a bearer token, and ends with an agent that asks nima before it acts: ask_knowledge_graph for who asked and why, search_code for where the code lives. Each page is a full file you can run, plus the same call over plain HTTP for when you would rather not speak MCP.
On for every workspace. The MCP server and API keys are on for every workspace. Every tool in a recipe is also a REST route with the same scopes and the same workspace boundary. Remote MCP server has the connection details, authentication and the full tool list. Knowledge tools documents ask_knowledge_graph, search_code and blast_radius, the tools these recipes call.
Pick a nima cookbook by framework
Choose the recipe that matches the agent framework you already run. Each card links to the recipe and shows its language.
MCP tools into a LangGraph agent, and one nima tool inside a custom graph node.
A remote MCP server on an Agent, filtered to the read tools for a reviewer.
The MCP connector on the Messages API, and classic tool use over REST.
An MCP client with streamable HTTP, tools into generateText and streamText.
An MCP toolset on an LlmAgent with a tool filter.
Before reviewing a diff, locate each touched file with search_code, ask what the change reaches with blast_radius, then pull the decisions behind every touched file.
Get an API key for a nima cookbook
Every recipe needs one personal API key with the knowledge:read scope, created in the web app under Settings, API keys. Any workspace member can create one. A key made without that scope gets a 403 on every recipe call. The key starts with nima_ and goes in the Authorization: Bearer header. Connecting with an API key covers keys, OAuth and scopes.
OAuth and identity
The userinfo endpoint and the OAuth 2.1 flow (discovery, registration, consent, token, refresh, revoke) that MCP clients and your own apps use.
LangChain and LangGraph
How to load nima's MCP tools into a LangChain agent with a personal API key, bind one into a LangGraph node, and fall back to plain HTTP.