APEX Everything MCP Server
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 |
|---|---|
| supermemory_searchC | Search Supermemory semantic long-term memory |
| supermemory_writeC | Write a memory to Supermemory |
| mem0_searchC | Search Mem0 semantic memory |
| aspen_searchC | Search Aspen local canonical truth store |
| memory_healthB | Check health of all memory substrates |
| llm_openaiC | Send prompt to openai LLM |
| llm_anthropicC | Send prompt to anthropic LLM |
| llm_groqC | Send prompt to groq LLM |
| llm_deepseekC | Send prompt to deepseek LLM |
| llm_openrouterC | Send prompt to openrouter LLM |
| llm_geminiC | Send prompt to Google Gemini |
| llm_cohereC | Send prompt to Cohere |
| llm_list_providersB | List all available LLM providers and their status |
| github_list_reposC | List GitHub repositories |
| github_search_codeC | Search code across GitHub repositories |
| github_create_issueC | Create a GitHub issue |
| github_get_repoC | Get GitHub repository details |
| gitlab_list_projectsC | List GitLab projects |
| dev_list_providersB | List all development tool providers |
| supabase_queryC | Query Supabase PostgreSQL database |
| supabase_list_tablesA | List all tables in Supabase database |
| pinecone_queryC | Query Pinecone vector database |
| neo4j_queryC | Query Neo4j graph database |
| db_list_providersA | List all database providers and their status |
| notion_searchC | Search Notion workspace |
| notion_create_pageD | Create a Notion page |
| slack_post_messageC | Post a message to Slack channel |
| linear_create_issueC | Create a Linear issue |
| pm_list_providersA | List all project management providers |
| vercel_list_projectsC | List Vercel projects |
| vercel_get_deploymentC | Get Vercel deployment details |
| render_list_servicesB | List Render services |
| railway_list_projectsB | List Railway projects |
| cloud_list_providersB | List all cloud/deploy providers |
| perplexity_searchC | Search with Perplexity AI (search-augmented generation) |
| perplexity_search_with_sourcesC | Search with Perplexity and get source citations |
| web_fetchC | Fetch and extract content from a URL |
| search_healthC | Check search/research provider health |
| smithers_skills_listA | List all registered Smithers skills |
| smithers_skill_getC | Get details of a specific skill |
| smithers_skill_executeD | Execute a Smithers skill |
| smithers_workflow_createC | Create a new workflow |
| smithers_workflow_listC | List all workflows |
| smithers_workflow_executeD | Execute a workflow |
| smithers_workflow_evolveD | Evolve a workflow based on metrics |
| smithers_mcp_listA | List all registered MCP servers |
| smithers_statusA | Get complete Smithers orchestrator status |
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 47 tools
Most tools are clearly distinguished by prefix and resource (e.g., github_, llm_, smithers_). However, there is some overlap between perplexity_search and perplexity_search_with_sources, and multiple search tools targeting different backends could cause confusion without careful descriptions.
Naming follows a consistent pattern: prefix_verb_noun or prefix_verb. All tools use snake_case with underscores, and the prefix clearly indicates the domain. No mixing of conventions.
With 47 tools, this server is on the high end. While the 'Everything' name justifies breadth, the number may overwhelm agents. The tool set could benefit from consolidation or more focused sub-servers.
Despite covering many domains, each domain is very shallow. For example, GitHub only has issue creation and repo listing, missing update/delete and pull requests. Many providers only offer list or query operations, lacking full CRUD.