Maguyva

What the Maguyva MCP server does

The Maguyva MCP server gives coding agents several ways to search code in repositories that have been indexed by Maguyva. Its supported search approaches include semantic search, structural or AST-oriented search, graph search, and full-text search. Together, these methods let an agent look for meaning, code structure, relationships, or exact text depending on the task.

The service is intended for repository analysis and code navigation. It supports more than 279 languages, according to the project documentation. The repositories must be indexed before the search capabilities can operate on them.

How it works

Maguyva is primarily exposed as a remote streamable-HTTP MCP endpoint at https://maguyva.tools/mcp. Clients that support remote MCP connections can send requests directly to that endpoint and provide an API key through an Authorization header.

For clients limited to stdio transport, the npm package @maguyva/mcp acts as a local bridge. The bridge reads MCP traffic from the client’s local stdio connection and forwards it to the remote Maguyva service. It can reconnect to the remote endpoint without dropping the local pipe.

The project also provides a usage skill based on the Agent Skills standard. The skill helps an agent choose among Maguyva’s search methods, recognize when ordinary local grep is preferable, and troubleshoot usage. Claude Code and Codex users receive the skill through the related plugin.

Setup and configuration

Get an API key from the Maguyva dashboard before configuring a client. For a client with remote MCP and custom authorization-header support, configure the service URL as https://maguyva.tools/mcp and send Authorization: Bearer <key>.

Use the stdio bridge only when the client cannot connect to a remote HTTP MCP server. The bridge requires Node.js and can be launched with npx -y @maguyva/mcp, passing MAGUYVA_API_KEY in the environment. The API key can instead be supplied with --api-key=KEY. Use --server=URL or MAGUYVA_SERVER_URL to replace the default endpoint.

Claude Code and OpenAI Codex can use the maguyva/agent-plugins plugin, which handles the HTTP connection and includes the skill and session guidance. The project’s installation documentation provides client-specific configuration formats for other supported clients.

The skill installer accepts client identifiers including claude, opencode, codex, cursor, vscode, gemini, cline, and agents. Claude Code and Codex plugin installations already include it.

Tools and capabilities

• Semantic search across indexed repository code
• Structural or AST-based code search
• Graph-based search for repository relationships
• Full-text search across indexed files
• Code intelligence covering 279+ languages

Limitations and notes

The remote service requires an API key, and searches apply to repositories indexed by Maguyva. This package does not provide a standalone local index; it is a transport bridge to the hosted endpoint. Clients that support remote MCP should generally use direct HTTP configuration instead of the stdio package.

The README does not specify individual MCP tool names, indexing workflows, repository synchronization behavior, or search-result schemas. The usage skill is recommended because it explains tool selection and the boundary between indexed search and local grep.