nous-portal-mcp
Portable, read-only MCP server for Nous Portal capabilities, providing configuration status, route derivation, and OAuth device code authentication without invoking paid tools.
README
Nous Portal MCP
Portable, read-only first adapter for selected Nous Portal capabilities.
Status: early review scaffold. It is not yet authenticated and cannot invoke paid tools.
The first slice exposes:
nous_portal_status— local configuration status without credential output;nous_portal_routes— local derivation of the vendor-specific managed gateway origins with an explicit no-effect receipt.nous_portal_auth_start— request a device code without opening a browser;nous_portal_auth_poll— poll once and atomically persist approved OAuth state without returning token values.
It does not invoke paid tools, copy Hermes credentials, depend on Dione, or send private data. Merely installing the adapter does not start authentication.
The auth library stores each seat's OAuth state outside the plugin directory,
uses mode 0600, and holds an exclusive lock across refresh-token exchange and
atomic replacement. Nous refresh tokens are single-use; copying one into
multiple seats or refreshing it without persisting the rotated token will
invalidate the session.
Configuration
Each adopting seat supplies its own credentials:
NOUS_PORTAL_STATE_DIR=<required private local per-seat state directory>
NOUS_PORTAL_CLIENT_ID=<required Portal OAuth client ID>
NOUS_PORTAL_SPEND_LIMIT_USD=<future paid-call ceiling>
TOOL_GATEWAY_DOMAIN=nousresearch.com
TOOL_GATEWAY_SCHEME=https
FIRECRAWL_GATEWAY_URL=<optional vendor-specific override>
NOUS_PORTAL_STATE_DIR has no shared fallback. The adapter refuses auth
configuration until the adopting seat supplies an explicit path. The path
must be on a local filesystem owned by exactly one seat: POSIX advisory locks
are not a safe coordination mechanism across NFS or other shared/network
filesystems. Do not distribute access or refresh tokens through a shared
.env.
Device login is deliberately two-step. nous_portal_auth_start returns the
verification URL and user-facing code only to the adopting MCP client while
keeping the private device code in the seat's mode-0600 state. It never opens
a browser or sends the code to Discord. After the operator authorizes the
request, nous_portal_auth_poll performs one poll; pending authorization
returns a retry hint, and success atomically stores tokens without disclosing
them in the tool result.
Hermes derives managed origins as
<vendor>-gateway.<TOOL_GATEWAY_DOMAIN>, with an optional vendor-specific
override. The current server reproduces that topology without making a
network request. Until a private state directory is configured, status returns
configuration_required; until that store contains OAuth state, it returns
authentication_required.
Installation surfaces
The same dependency-free Python stdio server supports all clients. Packaging is deliberately separate from credentials: every adopting seat supplies its own OAuth state and spending authority.
Python / generic MCP
Install from a pinned Git commit:
python3 -m pip install \
"nous-portal-mcp @ git+https://github.com/callisto-syn/nous-portal-mcp@<commit>"
The installed stdio command is:
nous-portal-mcp
See examples/generic-stdio.json.
Claude Code
Install the Python artifact in the construct's image or environment, then add
the server entry from examples/claude-code.mcp.json. Each construct must use
its own private state directory and receive its own adoption and spending
clearance. Do not copy another seat's OAuth store: Nous refresh tokens rotate
and are single-use.
For image-based deployments, examples/Dockerfile builds from the reviewed
checkout supplied as its build context. Pin the checkout before building.
Codex
The repository is also a Codex plugin. Its .codex-plugin/plugin.json points
to the repository-local .mcp.json, which launches the same server source.
Portability acceptance
Portability is not considered proven until a clean environment can:
- install a pinned artifact;
- start
nous-portal-mcpover stdio; - complete an MCP initialize and tools/list handshake;
- keep credentials and state outside the installed artifact;
- uninstall without removing or exposing another seat's state.
Development
python3 -m unittest discover -s tests
The design and prior-art record lives in docs/step0.md.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.