OpenTool
OfficialOpenTool
A self-hostable gateway for agent tools, with Supabase authentication, scoped agent keys, provider credentials, permissions, accounting reservations, REST, and MCP.
The runtime dispatches real provider requests. There is no demo fallback. Unconnected providers fail explicitly. The catalog contains 25 bounded operations; each needs its own permitted provider account. Automated contract tests are separate from paid-provider acceptance and must not be represented as live verification.
Supabase is the application database and authentication service. MCP uses expiring keys scoped to a single agent. Browserbase uses a separate bounded Node worker. Platform AI features must use OpenRouter; catalog lookup and provider execution do not require a model.
Internal accounting allowances are configured by the owner. They are not supplier-confirmed charges or guaranteed spending caps on a BYOK account. Pending and ambiguous outcomes retain reservations. Manual reconciliation records the owner's supplier reference and charge attestation.
This repository is not a security certification or a claim that every provider has passed paid acceptance. Release only after the deployment-specific gates in the development guide pass.
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/seven-hills-software/opentool'
If you have feedback or need assistance with the MCP directory API, please join our Discord server