greennode-agentbase-mcp
Officialby GreenNodeHub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP transport listen port. | 8080 |
| TOKEN_ENV | No | Name of the env var that holds the token, stdio only. Set this to read the token from a differently-named var. | GREENNODE_MCP_TOKEN |
| TRANSPORT | No | Transport mode: stdio or http. Defaults to stdio. | stdio |
| MAX_RESPONSE_BYTES | No | Hard cap on execute responses; over-cap responses are truncated with a notice. | 25000 |
| GREENNODE_MCP_TOKEN | No | Upstream bearer token, stdio only. Forwarded to all six services on execute. | |
| SEARCH_LIMIT_DEFAULT | No | Default limit for search_tools when the caller omits it. | 5 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/GreenNodeHub/greennode-agentbase-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server