Schema | nous-portal-mcp

nous-portal-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TOOL_GATEWAY_DOMAIN`	No	Gateway domain	nousresearch.com
`TOOL_GATEWAY_SCHEME`	No	Gateway scheme	https
`FIRECRAWL_GATEWAY_URL`	No	Optional vendor-specific override
`NOUS_PORTAL_CLIENT_ID`	Yes	Required Portal OAuth client ID
`NOUS_PORTAL_STATE_DIR`	Yes	Required private local per-seat state directory
`NOUS_PORTAL_SPEND_LIMIT_USD`	No	Future paid-call ceiling

Features and capabilities supported by this server

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
nous_portal_statusB	Report whether the portable Nous Portal adapter is configured. Never reveals credentials.
nous_portal_routesA	List locally derived Nous Portal vendor gateway routes. Makes no external request and invokes no paid tool.
nous_portal_auth_startA	Start a Nous Portal device-code login. Makes one unmetered external request, stores the private device code locally, and never opens a browser or sends the code to another channel.
nous_portal_auth_pollA	Poll a previously started device-code login exactly once. Makes one unmetered external request and atomically stores authorized tokens without returning token values.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/callisto-syn/nous-portal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server