You are three weeks into a tabletop campaign that has outgrown your notes. You have a folder of half-finished chapters, a public domain ghost story you love, and a vague idea that an agent could help you turn all of it into a world your players can explore. You already work with an AI agent every day. What you want is for it to reach into the tool where the world actually lives, instead of you pasting text back and forth.
So you go looking for what exists, and you land on a post from Hidden Door. Chris Wallace describes a Model Context Protocol server that lets, in the post's words, "the agents you already use to directly create, import, explore, and change worlds." It exposes the same capabilities creators already use in Atlas Studio, on top of what the company calls its narrative world model.
The post organises the server around four verbs. You can create a world from an idea. You can adapt existing writing into one. You can explore a world by asking it questions. And you can adjust tone, characters, and storylines. The demonstration is close to your own situation: it imports a Project Gutenberg copy of the Sleepy Hollow story, then folds a 1952 comic strip into it as a new storyline.
Then you get to the part that matters more than the demo, which is where the boundaries sit. "The MCP works on drafts," the post says. The agent saves to your account, and "it does not publish worlds or start games." Publishing and play stay in the human editor. If you have ever worried about an agent pushing something half-baked in front of your players, that line is the one you will remember.
The practical terms are just as plain. Access requires a Creator plan, and the first connection asks you to sign in through a browser. The plugin installs both the MCP connection and a curated set of skills that steer the agent through the tools. It launches as a beta, so you should expect rough edges. Still, a server that can write but cannot publish, with skills shipped alongside it, is a more careful first release than most consumer platforms manage.
Now you do what you would do with any provider you are weighing: you check the APIs.io catalog. And here the story turns on the catalog itself. The Hidden Door provider page has no API pages. Its record still says the company "publishes no developer API, SDK, or developer portal at this time."
That statement was true when it was written. But the post now names a remote endpoint at https://www.hiddendoor.co/mcp, setup instructions on the company's site, and a public plugins repository. That is exactly the evidence the profile needs in order to be redone. The catalog is not going to write the missing pages by hand. It is treating this story as a re-profile lead.
The numbers on the page show how stale the record is. The Kin Score is 12.2, in the emerging band, with discoverability at 48.2 and access clarity at 31.6. Contract quality, contract governance, and operational transparency all sit at 0.0. Agent Readiness is 0.0, human-only, with every dimension dark, the MCP server and agent skills included.
You read those figures carefully, because they could mislead you. They are not a verdict on what Hidden Door shipped. They are measurements of the old Hidden Door. The company's own post describes an agent surface with an auth flow, a scoped write boundary, and skills, three things the rubric rewards. The gap between a 0.0 and that description is simply the length of time between a launch and the next profile.
So here is what you take away. For your campaign, the post gives you enough to try it: a draft-only server, a Creator plan, a browser sign-in, and a beta label you should respect. For judging the provider, you trust the company's own account of its launch over a catalog score that has not caught up, while remembering that the post is the company's description and the catalog has not yet verified it. And for the catalog, you notice that even a record that was accurate when written can go quiet the day a company ships something new.
Read the original: https://apis.io/2026/11/10/hidden-door-opens-an-mcp-server-and-its-catalog-record-still-says-no-api/