Connect Claude, Cursor, ChatGPT, Codex, or any MCP-compatible client to Hollahoop. Triage feedback, update the roadmap, or publish an Update with a single sentence to your agent. No install, no SDK, just a URL and a token.
Claude Code 1.4.2 · connected to hollahoop-mcp · 2 read · 2 write
>Publish an update for what shipped this week. Keep it concise.
Workflows
One sentence moves the whole loop.
Feedback, roadmap and Updates are downstream of the same post status, so a single instruction to your agent cascades through all three. Three flows real Hollahoop teams run today:
01
Monday triage
“Close anything that looks like spam, tag the rest by area, and move the real ones into Reviewing.”
The Model Context Protocol is the language AI clients have settled on for reaching into other tools. Hollahoop speaks it natively, over HTTP, at hollahoop.app/mcp.
01
No install
Remote HTTP endpoint at hollahoop.app/mcp. No local package, no bridge process, no SDK. Paste a URL into your client config and you are done.
02
Full surface
Every MCP tool maps one-to-one to a Hollahoop API call, generated from the same schemas the dashboard uses. No stripped-down subset — an agent can do whatever a teammate with the same token could do.
03
Standard bearer auth
Tokens from Settings → API. Each one is scoped to a single org, carries explicit read or write permission, and is revocable from the same screen anytime. Nothing magic, nothing proprietary.
04
Any client
Cursor, Claude Code, Claude Desktop, ChatGPT, Codex, Windsurf, Copilot, Gemini today. Anything that supports remote HTTP MCP tomorrow — same URL, same auth.
Tool catalog
Everything your agent can do, on one page.
The MCP server exposes 14 tools, generated from the same schemas the dashboard uses. Read tools work with any token; write tools require a token with the write scope.
Read
· 8
Browse, search, fetch — safe for any agent.
list_projects
List every project the API key can see (scoped to a single Hollahoop organisation).
list_boards
List feedback boards on a project (e.g. feature-requests, bugs, general).
list_statuses
List the post-status workflow for a project (Open / Planned / In progress / Shipped / Declined and any custom ones).
list_posts
List feedback posts on a project, optionally filtered by board and/or status. Default sort is by vote count.
get_post
Fetch a single post by id, including its comments.
list_changelog
List changelog / Updates entries for a project (drafts and published).
list_docs
List documentation pages for a project, grouped by section. Use the `visibility` filter to scope to public or internal pages.
search
Free-text search across posts, changelog entries, and docs for a project. ILIKE-based for now; pgvector semantic search is on the roadmap.
Write
· 6
Mutating actions — gated by the write scope.
create_project
Create a new project under this API key’s organisation. Returns the project plus the URL of its public board. Default boards, statuses, changelog tags, and docs section are auto-seeded.
create_post
Create a new feedback / roadmap post. Defaults to the feature-requests board and the project default status (Open).
update_post_status
Move a post on the roadmap by changing its status. Use this to accept feedback (open → planned), start work (planned → in_progress), or ship (in_progress → shipped).
comment_on_post
Add a comment (or reply, via parent_id) to a post. The author is the user who created this API key.
publish_changelog
Create a changelog / Updates entry. Set publish=false to leave it as a draft. Auto-derives a slug from the title if none is given. The optional `tag` becomes the pill on the public Updates feed.
upsert_doc_page
Create or update a documentation page (uniquely identified by project + slug). Body is Markdown. Pass visibility=internal to keep the page hidden from the public site.
Open Cursor → Settings → MCP → Add new global MCP server, or edit the file directly.
Config location
macOS ~/.cursor/mcp.json
Windows %USERPROFILE%\.cursor\mcp.json
Linux ~/.cursor/mcp.json
Endpoint
The shape of the API, in one box.
URL
https://hollahoop.app/mcp
Transport
HTTP / JSON-RPC 2.0
Protocol
MCP 2025-06-18
Auth
Authorization: Bearer hh_live_…
The same URL serves initialize, tools/list and tools/call. A plain GET with Accept: application/json returns a self-describing manifest you can paste into any other tool that expects one.
Questions
Frequently asked, plainly answered.
What is the Hollahoop MCP server?
A remote Model Context Protocol endpoint that exposes Hollahoop’s feedback, roadmap, Updates and docs to AI agents. Your agent calls the same code paths the dashboard does — nothing more, nothing less.
Do I need to install anything?
No. Hollahoop MCP is remote HTTP. There is no bridge process, no SDK, no local package — every supported client connects to the same URL with a bearer token.
Which clients are supported?
Anything that speaks remote HTTP MCP with custom headers. Ready-to-paste configs for Cursor, Claude Code, Claude Desktop, ChatGPT, Codex and Windsurf live in the Setup section above. Copilot, Gemini CLI, Continue, Zed and OpenCode also work — same URL, same auth.
How does authentication work?
Bearer tokens scoped to one org, generated from Settings → API. Tokens carry explicit read or write scope and act as the user who created them for audit purposes. Revoke from the same screen, takes effect on the next request.
What can an agent actually do, and can it delete things?
Read everything: projects, boards, posts, comments, Updates, docs, statuses. Write a lot: create posts, change post statuses, comment, publish Update drafts, upsert documentation pages. Destructive operations (deleting posts, dropping orgs) are deliberately not exposed to the MCP surface.
MCP vs the REST API: which should I use?
They are the same surface. The MCP server is a structured wrapper around the same endpoints; if you are wiring up an AI agent, use MCP. If you are building a script or a server-side integration that does not involve an LLM, hit the REST API directly with the same token.
Is MCP included in all plans?
Yes. The MCP server ships free on every plan, including Free, with the same rate limits the dashboard enjoys. Higher rate limits and SSO unlock on Starter and Professional, but the protocol itself is universal.
Is my data or token sent anywhere else?
No. Your token authenticates directly against hollahoop.app/mcp and never touches the AI client provider. Tool calls happen server-to-server between your agent runtime and Hollahoop.
Hand Hollahoop to your agent.
Grab an API token, paste the MCP endpoint into your client, and ask your agent to do something it could not do an hour ago. That is what the loop, on autopilot, looks like.