plugandship-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLUGANDSHIP_API_URL | No | API base URL (use http://localhost:3000 against a local site). | https://plugandship.dev |
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 |
|---|---|
| search_toolsA | Search the Plug and Ship index of MCP servers, agent skills (SKILL.md) and coding-agent plugins. Results are ranked by name match, then GitHub stars, and include install commands. Use client to narrow to a coding agent (grok-bot returns only MCP servers with a public HTTPS endpoint). |
| get_toolA | Full details for one tool by its Plug and Ship slug (from search_tools): description, stars, install command, remote endpoint, license, tags and last commit. |
| trendingA | New MCP servers, skills and plugins created on GitHub in the period, ranked by stars gained per day since creation. |
| list_bestB | A ranked best-of list by topic, e.g. 'grok-bot-connectors', 'voice-agents', 'local-models', 'figma-mcp-servers', 'mcp-servers-for-databases'. Omit topic to list all topics. |
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 distinct role: list_best surfaces curated topic rankings, search_tools queries the index, get_tool fetches one slug's detail, and trending ranks new items by star velocity. The only mild overlap is between list_best and trending, both being ranked lists, but their framing (topic vs recency) keeps them separable.
Three tools follow a clean verb_noun pattern (list_best, search_tools, get_tool). trending breaks the pattern with a bare gerund/noun, a minor deviation but not confusing.
Four tools is on the lean side but fits a compact directory/index API where search plus detail plus two curated views is the core surface. Nothing feels redundant or dead-weight.
The lifecycle of discover (search_tools/list_best/trending) and inspect (get_tool) is covered, and list_best with no topic effectively enumerates topics. Minor gaps exist, such as tag/language filtering or explicit topic enumeration, but the core workflow is intact.