api-mind
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPECS_DIR | Yes | Absolute path to the directory containing .mind spec files. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| list_apisA | Lists all APIs loaded from the specs folder, with their names, titles, base URLs, and available environments. Use this when you need to know what APIs are loaded or what environments a specific API supports. Call this first when the user references an API you haven't seen yet. | ||||||||||||
| list_endpointsA | Lists all available endpoints across all loaded .mind files. Also surfaces the available environment names. Use this to discover what endpoints exist across all APIs. Filter by method, path, or section. Call this when the user references an API or asks what's available. | ||||||||||||
| get_endpoint_schemaA | Returns the full context for a specific endpoint including resolved URL, auth requirements, and schema. Use this to understand an endpoint before constructing a curl command to execute via the bash tool. Call this after list_endpoints to get the endpoint contract. Auth Patterns
NOTATION Legend
| ||||||||||||
| get_call_contextA | Returns the runtime context needed to execute API calls: resolved base URL, active environment, and default values for credentials and parameters. Call this before constructing a curl command when the user wants to actually invoke an endpoint. Do NOT call this just to browse or understand the API shape — use list_endpoints and get_endpoint_schema for that. Reads from ~/.config/api-mind/.env and ~/.config/api-mind//.env. Defaults to "dev" unless the user specifies otherwise. |
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/msegoviadev/api-mind-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server