Add Shiro (Remote) MCP server
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
Research direction
Read the registry criteria for proprietary service references and compare the proposed entry with registries/toolhive/servers/notion-remote/server.json. Add registries/toolhive/servers/shiro-remote/server.json with the described remote endpoint and authentication setup. Done when the entry follows the existing remote server shape and meets the stated registry requirements.
Written by the indexing model from the issue text.
Description
MCP Server Information
Server Name: Shiro (Remote)
Repository URL: https://github.com/meetshiro/shiro-mcp
Brief Description: Work on a novel or non-fiction book in Shiro: read scenes and the outline, edit prose, fill characters and places, check continuity and export EPUB. Every change is kept in the project's History.
This is Shiro's own hosted server, so I'd add it as a first-party remote entry under the proprietary service references rule:
- Endpoint:
https://api.meetshiro.com/mcp(Streamable HTTP) - Auth: OAuth 2.1 with PKCE (S256) and dynamic client registration, advertised in
/.well-known/oauth-protected-resource/mcpand/.well-known/oauth-authorization-server. No API key. A free Shiro account is enough - Official MCP Registry:
io.github.meetshiro/shiro(active, latest) - Docs: https://meetshiro.com/agents/
- Workflow: a writer connects ToolHive to their Shiro project, then asks the agent to read the outline, revise a scene, fill a character's World entry or run a continuity check. Every write lands in the project's History, where the writer can restore an earlier version
The planned entry is registries/toolhive/servers/shiro-remote/server.json, with remotes and no oauth_config, the same shape as notion-remote.
I work on Shiro.
Basic Requirements
- Open Source: the repository above (connection config, skill, plugin manifests) is MIT. The hosted server is proprietary and published by the vendor, which the proprietary service references rule allows
- MCP Compliant: Implements MCP API specification
- Active Development: Recent commits and maintained
- Documentation: https://meetshiro.com/agents/ and the repository README
- Security Contact: [email protected]
Submitter Checklist
- I have read the MCP Server Registry Inclusion Heuristics
- This server meets the basic requirements listed above (all but the open source item, explained there)
- I understand this will undergo automated and manual review based on Registry Management
- Dominant language
- Go
- Stars
- 26
- Forks
- 104
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 69
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stacklok/toolhive-catalog
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
stacklok/toolhive-catalog#1929 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
stacklok/toolhive-catalog#1918 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
stacklok/toolhive-catalog#1914 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
stacklok/toolhive-catalog#1909 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
stacklok/toolhive-catalog#1908 ·
Maintainers usually reply within 1 day
All issues in stacklok/toolhive-catalog
Similar issues
-
area/networking kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
siderolabs/talos#14972 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
kubectl wait outputs cryptic "error: unrecognized condition: []" when --for is omittedPossibly taken @muskan-creates352 claimed this today. Openkind/bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
kubernetes/kubectl#1910 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
unbound-force/gaze#353 ·
Maintainers usually reply within 1 day
-
bug cross-seed ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day