
Hermes (Vajro)
io.github.gndeepanPublished by GitHub account gndeepanv0.3.0Updated Oct 24, 2026
Manage a Vajro store through the Hermes API: themes, blocks, settings, plugins and more.
Overview
Lets an assistant manage a Vajro store through the Hermes API, covering themes, blocks, settings and plugins.
- What you can do
- This remote MCP server connects an assistant to the Hermes API for a Vajro store. According to the description, it lets the assistant work with store themes, blocks, settings, plugins and related configuration. The manifest does not list individual tools, so the exact operations available are not documented here.
- When to use it
- Use it when you want an AI assistant to help configure or maintain a Vajro storefront through Hermes, such as adjusting themes, blocks, settings or plugins, rather than doing those tasks by hand in the store admin.
- Requirements
- A remote streamable HTTP endpoint. A Hermes access token is required in the Authorization header as a bearer token. The X-Store-Id header is required to select the store. An optional X-Refresh-Token header lets the server renew an expired access token. No local runtime or packages are needed.
Installation
In SourceWeft
- Open Hermes (Vajro) in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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/io.github.gndeepan%2Fhermes-mcp/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"hermes-vajro": {
"type": "http",
"url": "https://hermes_mcp_host/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v0.3.0LatestOct 12, 2026
Score
39% of the applicable checks met
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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- 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.