Where it fits
Teams that publish HTML reports and proposals and need feedback and revisions at one stable link.
- Publish an HTML report and collect feedback.
- Share a proposal and publish a revision.
- Keep an interactive page at one link.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Shareout
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Use when starting any conversation. Establishes how to find and use skills and requires Skill tool invocation before any response, including clarifying questions.
Ask which skill or flow fits a situation. It routes among the user-invoked skills in this repository.
Searches, creates, and manages notes in an Obsidian vault with wikilinks and index notes. Use it when the user wants to find, create, or organize notes in Obsidian.
No skills found
Try a different search term or clear the filters.
Add Shareout to your client
Add the remote endpoint and complete OAuth in the browser. Codex needs one extra command, codex mcp login shareout, after the server is in .codex/config.toml.
- Add the remote server
Register https://shareout.io/mcp as a remote Streamable HTTP server in OpenCode, Claude Code, Claude Desktop, or another client.
- Sign in with OAuth
Complete the provider sign-in when the client prompts.
- Codex: complete the MCP login
For the MCP-only Codex connection, run this after adding the server to .codex/config.toml.
codex mcp login shareout
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name shareout. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
shareoutappears and that the tools match the provider documentation. - 2Run one small request.
Start with: Publish an HTML report and collect feedback. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Shareout repositoryhttps://github.com/geland/shareout-integrations#codex