LangChain registry-mcp — national company registries Resource/rules_no
How to: LangChain registry-mcp — national company registries rules_no
Add registry-mcp — national company registries to LangChain
-
01
Open pip install langchain-mcp-adapters and merge this in. Keep any servers already there.
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient({
"registry-mcp": {
"transport": "streamable_http",
"url": "https://api.foretak.dev/mcp",
}
})
tools = await client.get_tools()
-
02
Save the file and restart LangChain.
-
03
rules_no is surfaced through the client's resource API, read by URI. It is context to attach, not an action to run.
-
04
If it does not appear, check that registry-mcp — national company registries is connected and that you are looking at its resources rather than its tools.
get_tools() returns the server's tools as LangChain tools, ready for an agent. LangChain docs
Set these first
registry-mcp — national company registries will not start until these are set, so it never reaches LangChain.
-
REGISTRY_MCP_CONTACT_EMAIL -
REGISTRY_MCP_CACHE_PATH -
COMPANIES_HOUSE_API_KEY -
BOLAGSVERKET_CLIENT_ID -
BOLAGSVERKET_CLIENT_SECRET -
BOLAGSVERKET_ENVIRONMENT
Same resource, other clients
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.