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 175+ 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 introduces the product, get_started guides installation, connect_client explains client integration, and list_connectors catalogs integrations. No overlap or ambiguity.
All tools follow a consistent 'anythingmcp_verb_noun' pattern (connect_client, get_started, list_connectors, overview). The naming is uniform and predictable.
With 4 tools, the set is tightly scoped to the server's purpose of onboarding and exploring AnythingMCP. Each tool earns its place, and the count is appropriate for the domain.
The tools cover the core user journey: overview, installation, client connection, and integration discovery. Minor gaps exist (e.g., no tool for advanced configuration or troubleshooting), but the essential needs are met.