Orbit-MCP
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello_orbitC | Test connectivity and show Orbit-MCP status |
| list_available_serversA | List all available MCP servers from Docker MCP catalog Returns a list of server dictionaries with name, description, and status. Use this to see what servers you can enable with enable_server. |
| enable_serverA | Enable a specific Docker MCP server by name (with OAuth-first authentication) Args: server_name: Name of the server to enable (e.g., 'github', 'slack', 'notion') Returns: Dictionary with success status, message, and authentication details |
| list_enabled_serversA | List currently enabled MCP servers Returns a list of enabled server dictionaries with name, status, and container info. |
| list_oauth_providersA | List available OAuth providers and their authorization status Returns a list of OAuth providers with their authorization status. Use this to see which services support OAuth and whether they're authorized. |
| authorize_oauthA | Start OAuth authorization flow for a provider (e.g., 'github', 'gdrive') Args: provider: OAuth provider name (e.g., 'github', 'gdrive') Returns: Dictionary with success status and authorization details |
| revoke_oauthA | Revoke OAuth authorization for a provider Args: provider: OAuth provider name (e.g., 'github', 'gdrive') Returns: Dictionary with success status and revocation details |
| disable_serverA | Disable a specific Docker MCP server by name Args: server_name: Name of the server to disable (e.g., 'github', 'slack', 'notion') Returns: Dictionary with success status and server removal details |
| reset_all_serversA | Disable all currently enabled MCP servers (company reset functionality) Returns: Dictionary with success status and list of disabled servers |
| check_server_authA | Check authentication requirements and status for a server Args: server_name: Name of the server to check (e.g., 'github', 'slack') Returns: Dictionary with authentication requirements and current status |
| start_gatewayA | Start the Docker MCP Gateway for tool execution Returns: Dictionary with success status and gateway details |
| stop_gatewayA | Stop the Docker MCP Gateway Returns: Dictionary with success status and details |
| gateway_statusA | Check the status of the Docker MCP Gateway Returns: Dictionary with gateway status and details |
| discover_gateway_toolsB | Discover tools available from enabled Docker MCP servers Returns: List of tool definitions from enabled servers |
| call_gateway_toolA | Call a tool from enabled Docker MCP servers Args: tool_name: Name of the tool to call (e.g., 'create_issue', 'search_repositories') arguments: Dictionary of arguments to pass to the tool Returns: Dictionary with tool execution result |
| list_enabled_toolsA | List all available tools from currently enabled servers Returns a list of tool dictionaries with name, description, and server info. Use this after enabling servers to see what tools are available. |
| create_packA | Create a new company/team pack with specific MCP servers Args: pack_name: Name of the pack (e.g., 'frontend-stack', 'acme-devops') description: Human-readable description of the pack servers: List of server names to include in the pack tags: Optional list of tags for categorization (e.g., ['frontend', 'development']) Returns: Dictionary with success status and pack creation details |
| install_packA | Install a pack by enabling all its servers Args: pack_name: Name of the pack to install (e.g., 'frontend-stack') enable_oauth: Whether to prompt for OAuth authorization if needed Returns: Dictionary with installation results and any auth requirements |
| uninstall_packA | Uninstall a pack by disabling all its servers Args: pack_name: Name of the pack to uninstall Returns: Dictionary with uninstallation results |
| list_packsA | List all available company/team packs Returns: List of pack configurations with server details |
| get_pack_infoA | Get detailed information about a specific pack Args: pack_name: Name of the pack to inspect Returns: Dictionary with pack information and server status |
| create_company_pack_templateA | Create a predefined company pack from templates Args: template_name: Name of the template ('frontend-stack', 'backend-stack', 'devops-stack', 'data-stack', 'productivity-stack', 'web-scraping-stack') Returns: Dictionary with pack creation results |
| update_packB | Update an existing pack with new configuration Args: pack_name: Name of the pack to update description: New description (optional) servers: New list of servers (optional) tags: New list of tags (optional) Returns: Dictionary with success status and update details |
| add_server_to_packA | Add a server to an existing pack Args: pack_name: Name of the pack server_name: Name of the server to add Returns: Dictionary with success status and operation details |
| remove_server_from_packA | Remove a server from an existing pack Args: pack_name: Name of the pack server_name: Name of the server to remove Returns: Dictionary with success status and operation details |
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/Wirasm/orbit-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server