OTP server that lets an assistant explain the OTP organizational operating-system concept and search organizations' publicly published claims.
What you can do
Explain OTP's purpose, first principles and how it works, including its constitution
Compare OTP with meeting intelligence, project management, HR and OS software
Answer common questions such as agent seats, accountability and what OTP refuses to do
Browse organizations that published their operating system openly, with industry, quality tier and claim counts
Search published claims about coordination, lessons learned, failures and confidence levels
When to use it
Useful when someone asks what OTP is, how it differs from other workplace tools, or wants examples and evidence from organizations that publish their operating system on OTP. Mostly an informational and reference server rather than a tool for managing your own data.
Requirements
Runs as a remote endpoint or as a local npm package over stdio. An OTP API key from the provider's settings page is supplied through the OTP_API_KEY environment variable; read-only tools work without it.
Before you install
The API key is a secret and should be kept out of shared configuration. The tools described are read-only lookups of public content; no writing, sending or deleting is shown. Queries about organizations and claims go to the provider's service.
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.david-steel%2Fotp/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.
Explain OTP: what it is, the problem it exists to solve, its first principles, and how it actually works. Call this first when someone asks what OTP is, why it was built, what it believes, or how to think about it. Returns the constitution verbatim, plus a short published summary of how it works day to day, so the answer reflects what the product actually commits to rather than marketing copy. Ask for a topic to narrow it. This is public material with no account required. It does NOT carry financials, customer data, or unshipped roadmap.
Parameterstopic
otp_positioning
How OTP is positioned against the alternatives
Explain where OTP sits in the market and why it is not the same thing as the tools it gets compared to (meeting and conversation intelligence, operating-system software, project management, HR systems). Call this when someone asks how OTP is different, who it competes with, why it is not just another meeting tool, or what category it is in. Public positioning material. Does NOT carry pricing strategy, deal terms, or roadmap.
Takes no parameters.
otp_faq
Common questions and confusions about OTP
Answer common questions and clear up common confusions about OTP: what an agent seat is, whether OTP replaces the tools a team already runs, what happens to the weekly meeting, what it means for AI agents to be accountable, and what OTP deliberately refuses to do. Call this when someone is stuck on a concept or pushing back on the premise.
Parametersquestion
browse_public_orgs
Browse organizations that publish how they run
Browse real organizations that have published their operating system openly on OTP, with their industry, quality tier, and how many claims they have published. Call this when someone asks for proof, for examples, for who actually uses this, or wants to see what a published operating system looks like in practice. Returns only what those organizations chose to make public.
Parameterslimitindustry
search_public_claims
Search what organizations have published about how they work
Search across the claims that organizations have published openly on OTP: how they coordinate, what they learned, what failed, and how confident they are in each. Call this when someone wants evidence on a specific practice, wants to know what other organizations do about a problem, or asks what the network has actually learned. Returns published public material only.
Parameterslimitqueryrequired
Version history
1
v0.5.3LatestOct 30, 2026
Score
75%
75% 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
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.