Use a published MCP entry
Find One Horizon in Smithery instead of maintaining a private server definition for every client
Integration
Add One Horizon to your MCP stack through Smithery
Use the published Smithery server entry to give compatible clients access to One Horizon initiatives, bugs, todos, recaps, teams, taxonomy, and comments.
AI assistants and coding agents
Smithery
One Horizon
Use a published MCP entry
Authorize workspace access
Bring work tools into more clients
Authorize workspace access
Connect through OAuth so the tools act with the permissions of the signed-in One Horizon user
Bring work tools into more clients
Use Smithery-supported MCP environments to read and update One Horizon work
A registry path into the One Horizon MCP server
Smithery handles discovery and connection while One Horizon remains the source for product and engineering work.
Find the official server entry
Use the published onehorizon/onehorizon listing from the Smithery UI or CLI.
Browse available work tools
Discover actions for initiatives, bugs, feature requests, todos, recaps, teams, taxonomy, and comments.
Call tools from a compatible client
Use the connected server entry wherever your Smithery-enabled MCP workflow runs.
For teams managing MCP connections with Smithery
Add One Horizon to the same registry workflow used for the rest of your MCP servers.
MCP client setup
Connect the published server entry to a new assistant or development environment
Tool discovery
Inspect available One Horizon actions before deciding what the client should be allowed to do
Registry-managed access
Use Smithery connection IDs and OAuth to keep the server available across supported clients
Connect One Horizon through Smithery
Open the published server entry and bring live product work into your MCP environment.