docs(typeform): correct EU hosts, scopes, and the capability table

[pol-borrellas]

Hi — I work at Typeform. Three factual corrections to our plugin's README, all verified against the live MCP server rather than inferred. README only; plugin.json and mcp.json are untouched.

1. The two EU hosts aren't interchangeable

The page offered api.eu.typeform.com or api.typeform.eu "depending on where your account lives", which reads as two spellings of the same thing. They're different:

Account	Server URL	Authorization server
Default data center	https://api.typeform.com/mcp	https://api.typeform.com
EU data center	https://api.eu.typeform.com/mcp	https://api.typeform.com
typeform.eu	https://api.typeform.eu/mcp	https://api.typeform.eu

api.typeform.eu has its own issuer, token endpoint, and JWKS, so tokens don't move between the two. Verified from each host's /.well-known/oauth-protected-resource. This is the one most worth fixing: picking the wrong host fails partway through the OAuth exchange, not at install time, so it presents as a confusing auth bug.

2. The capability table was missing two categories

Themes and Automations weren't listed at all, and the Forms row didn't mention editing or publishing. Agents reading this table won't try what they can't see.

3. The scope list named 7 of 14

The server's 401 challenge advertises accounts:read, automations:read, automations:write, contacts:read, contacts:write, forms:read, forms:write, insights:read, responses:read, responses:write, webhooks:read, webhooks:write, workspaces:read, workspaces:write.

---

Everything else checked out and I left it alone — the OAuth-only note is right, personal access tokens are rejected, there's no SSE endpoint (/mcp/sse and /sse both 404), and the docs link 301s correctly to its canonical target.

Happy to adjust tone or trim any of this to match how you'd rather the directory read. If it's useful, we can also review future changes to this plugin before they ship.

🤖 Generated with Claude Code

---

Note

Low Risk
README-only factual corrections with no runtime, config, or security code changes.

Overview
Documentation-only update to the Typeform plugin README so setup and agent capabilities match the live MCP server.

The Before you connect section now spells out default vs two EU endpoints in a table (MCP URL and authorization server), explains that api.typeform.eu is a separate OAuth stack with non-portable tokens, and notes Enterprise-only EU hosting.

The What agents can do table adds Themes and Automations, expands Forms (edit/publish) and Contacts (lists, bulk upsert, mapping), and lightly rewords workspaces/accounts.

Notes and Docs refresh the OAuth scope list to the full set advertised by the server (including automations, responses, webhooks, and workspace write), replace the beta/limited-capabilities wording with active-expansion language, drop the post-auth empty-tools refresh tip, and point to updated developer/help URLs.

^{Reviewed by Cursor Bugbot for commit 7f48ddb. Bugbot is set up for automated code reviews on this repo. Configure here.}

[pol-borrellas]

Hello, @SamSokolin !

I'm Pol, the Lead PM in charge of Typeform's MCP server.

Could you merge this PR updating the README file on Typeform's MCP server, please?

Thanks!