A remote MCP server for searching the Invokera tool catalog, inspecting a tool's schema and endpoint, and invoking publicly enabled tools.
What you can do
Search the Invokera catalog for published tools across all projects, returning a ranked list of names, projects, summaries and categories without input schemas. Retrieve the full JSON Schema and calling instructions for a chosen tool, including the exact REST or MCP endpoint to call it on. Invoke tools whose owners have enabled public invocation, passing the project slug, tool name and arguments.
When to use it
Useful when you want an assistant to discover tools published on Invokera and either call publicly enabled ones directly or learn how to call the rest with the owner's token.
Requirements
A remote streamable HTTP endpoint at invokera.com; no packages, environment variables or headers are declared. Calling tools that are not publicly enabled requires that project's own endpoint token, obtained from its owner.
Before you install
Invoking a tool runs third-party code and usage is metered to the tool owner, so calls may incur costs. Tools not opted in for public invocation return not-found and need the project's token, which is a credential to handle carefully.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.invokera%2Fdiscover/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Search the Invokera catalog for published tools across all projects. Returns a ranked list of tools (name, project, summary, category) WITHOUT their input schemas. Call describe_tool next to get the full schema and calling instructions for a specific tool.
Parameterslimitquerycategory
describe_tool
Get the full input schema and calling instructions for one tool found via search_tools. Returns the JSON Schema plus the exact REST/MCP endpoint to call it on. Calling a tool requires that project's own endpoint token, obtained from its owner.
Parameterstool_namerequiredproject_slugrequired
invoke_tool
Call a tool whose owner has enabled public invocation, without needing that project's token. Only works for tools opted in by their owner; others return not-found (use describe_tool for how to call them with a token). Usage is metered to the tool owner. Get project_slug/tool_name and the argument schema from search_tools + describe_tool first.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.