anythingmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| anythingmcp_overviewA | Read-only, no side effects. Returns a concise plain-text overview of AnythingMCP (a self-hosted, no-code MCP gateway) with links to the website, GitHub repo and cloud. Call this FIRST to understand the product; then use anythingmcp_get_started to install it, anythingmcp_connect_client to wire up an AI client, or anythingmcp_list_connectors to browse integrations. |
| anythingmcp_get_startedA | Read-only, no side effects. Returns copy-pasteable plain-text steps to install and run your own AnythingMCP gateway in ~60 seconds (self-host with Docker, or the managed cloud). Use this when you want to DEPLOY AnythingMCP; to connect an already-running instance to an AI client, use anythingmcp_connect_client instead. |
| anythingmcp_connect_clientA | Read-only, no side effects. Returns plain-text setup instructions for connecting ONE AI client to an AnythingMCP server; pass the required |
| anythingmcp_list_connectorsA | Read-only, no side effects. Returns a plain-text catalog of AnythingMCP's 543 pre-built connectors grouped by category (logistics, ERP, e-commerce, HR, public data, banking, messaging, sports), plus the 5 connector types you can build with no code (REST, SOAP/WSDL, GraphQL, Database, MCP-bridge), with a link to the full list. Use this to discover available integrations before connecting a client. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: overview, install/run, connect a client, and browse connectors. Descriptions explicitly cross-reference adjacent tools, making misselection unlikely.
All four tools follow a consistent prefix plus snake_case verb_noun pattern: anythingmcp_overview, anythingmcp_get_started, anythingmcp_connect_client, anythingmcp_list_connectors.
Four tools are well-scoped for an onboarding/discovery server. Each tool covers a distinct stage of the user journey without unnecessary surface area.
The surface covers the core journey from product overview to installation, client connection, and connector discovery. Minor gaps include no connector search/filter or detailed connector lookup, but the stated purpose is largely met.