LangGraph agents and Dome
Keep your graph, and govern every call it makes. Point a LangGraph agent's model and tools at Dome and its graph stays as it is. Every model call and every tool call is checked against your rules and recorded against the agent.
Dome governs every tool and model callin LangGraph.
No rewrite
Nodes, edges and state stay as they are. The model client and the tool list change.
Tools from the Gateway
The graph loads its tools from the Gateway's MCP endpoint. It sees only the tools its agent is granted.
Every call on the record
Model and tool calls land in one audit trail, against the agent and the person it acted for. Retries show as attempts of their own.
LangGraph on Domein two changes.
Swap the chat model for one that calls the Model Broker, and load tools from the Gateway over MCP, leaving the graph itself untouched.
Install the packages
Install Dome's LangChain adapter and LangChain's MCP adapters on Python 3.12 or later.
shellpip install dome-langchain langchain-mcp-adapters langgraphLoad tools from the Gateway
The Gateway's MCP endpoint serves the tools this agent is granted, with their real schemas.
pythonfrom langchain_mcp_adapters.client import MultiServerMCPClient mcp = MultiServerMCPClient({"dome": { "transport": "streamable_http", "url": f"{GATEWAY_URL}/mcp", "headers": {"Authorization": f"Bearer {DOME_AGENT_KEY}"},}})tools = await mcp.get_tools()Call models through the Broker
The model name is a pool, so failover across providers comes with it.
pythonfrom dome_langchain import AgentIdentity, DomeChatOpenAI llm = DomeChatOpenAI.for_agent( AgentIdentity(token=DOME_AGENT_KEY, gateway_url=GATEWAY_URL), model="claude-opus-5-5",).bind_tools(tools)
One agent,end to end.
A two-node graph: a model node on Opus through the Broker and a ToolNode fed by the Gateway. Its Dome key is the only credential it holds.
researcher
Answer questions about the code
The graph loops between Opus and the GitHub tools until the question is answered. Each tool call is decided at the Gateway, each model call routed by the Broker.
python
from langchain_mcp_adapters.client import MultiServerMCPClientfrom langgraph.graph import START, MessagesState, StateGraphfrom langgraph.prebuilt import ToolNode, tools_conditionfrom dome_langchain import AgentIdentity, DomeChatOpenAI
async def build_researcher(): # Tools: whatever this agent is granted on the Gateway mcp = MultiServerMCPClient({"dome": { "transport": "streamable_http", "url": f"{GATEWAY_URL}/mcp", "headers": {"Authorization": f"Bearer {DOME_AGENT_KEY}"}, }}) tools = await mcp.get_tools()
# Model: a pool on the Broker, with failover across providers llm = DomeChatOpenAI.for_agent( AgentIdentity(token=DOME_AGENT_KEY, gateway_url=GATEWAY_URL), model="claude-opus-5-5", ).bind_tools(tools)
async def think(state: MessagesState): return {"messages": [await llm.ainvoke(state["messages"])]}
graph = StateGraph(MessagesState) graph.add_node("think", think) graph.add_node("tools", ToolNode(tools)) graph.add_edge(START, "think") graph.add_conditional_edges("think", tools_condition) graph.add_edge("tools", "think") return graph.compile()
researcher = await build_researcher()await researcher.ainvoke({"messages": [("user", "Where is rate limiting handled?")]})Bringing it alltogether.
Connecting LangGraph agents to tools, models, and identity in Dome completes a governed agent application.
Acting for
Agent
LangGraphRuntime
Control point
GatewayEvery call decided and audited
RulesGuardsQuotas
Common questionsabout LangGraph.
More of whatDome works with.
Model
Claude Fable
Fable 5.1 from Anthropic and Amazon Bedrock in one failover pool, open to one group and capped by quota.
Provider
OpenAI
The OpenAI API behind the Model Broker: the key held in Dome, every call authorized, metered and audited.
MCP server
Atlassian
The Atlassian Rovo MCP server behind the Tool Gateway, with rules that decide each Jira and Confluence call on its tool and site.
Identity
Microsoft Entra ID
Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
Client
Claude Code
Claude Code on a Dome Gateway with per-developer sign-in, rules on every tool call, and audit by name.
Agent service
TinyFish
TinyFish's web agents behind the Tool Gateway, with rules that decide each run on the site it targets.
Talk with ourFDE team.
Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.
Talk with our FDE team
Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.
Agent frameworks and runtimes: govern agents without a rewrite
Build agents on the framework you already use. Dome governs their tool and model calls without a rewrite.