nous-portal-mcp

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.

Category
访问服务器

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:

  1. install a pinned artifact;
  2. start nous-portal-mcp over stdio;
  3. complete an MCP initialize and tools/list handshake;
  4. keep credentials and state outside the installed artifact;
  5. 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.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选