NLocq
Expose ChainContext’s NLocq remote MCP endpoint so your coding agent can query chain-context data over streamable HTTP during backend or agent builds.
Overview
NLocq is a MCP server for the Build phase that exposes ChainContext’s NLocq capabilities to coding agents via a hosted streamable-HTTP endpoint.
What is this MCP server?
- Streamable-HTTP remote at nlocq.chaincontext.dev (registry schema 2025-12-11)
- Published as chaincontext publisher tooling v1.0.0
- Server version 1.0.0 with no local package install in registry metadata
- Suited as a thin context bridge for agent workflows that already use MCP clients
- Registry server version 1.0.0
- Publisher tooling chaincontext v1.0.0
- Single streamable-HTTP remote URL documented in server.json
What problem does it solve?
You need your agent to reach ChainContext-hosted context without maintaining a custom client integration.
Who is it for?
Builders already on MCP who want a hosted ChainContext remote with minimal local setup.
Skip if: Teams that need documented tool lists, offline-only stdio MCP, or full feature clarity before adoption.
What do I get? / Deliverables
After you register the remote MCP URL, your agent can invoke NLocq through the same MCP configuration you use for other HTTP servers.
- Registered HTTP MCP remote in your agent config
- Callable NLocq tools once verified against the live endpoint
Recommended MCP Servers
Journey fit
Remote MCP registration belongs in Build when you wire agent tooling to external context services before shipping automation. Integrations is the canonical shelf for third-party HTTP MCP remotes that extend what the agent can call at dev time.
How it compares
Hosted MCP remote integration, not a local PyPI/npm MCP package with enumerated tools in the registry.
Common Questions / FAQ
Who is dev.chaincontext/nlocq for?
Solo builders and small teams using MCP clients who want to attach ChainContext’s NLocq HTTP endpoint to Claude Code, Cursor, or compatible agents.
When should I use dev.chaincontext/nlocq?
Use it during Build when you are wiring agent integrations and ChainContext’s hosted NLocq service matches the context queries your workflow needs.
How do I add dev.chaincontext/nlocq to my agent?
Add the streamable-HTTP remote URL https://nlocq.chaincontext.dev to your agent’s MCP server config per your client’s HTTP MCP setup docs, then verify available tools in the client UI.