This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · heyhey.dev
51tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://heyhey.dev/mcp
Skill page: https://www.mcpbundles.com/skills/heyhey-mcp-5b3b6e4af6
Explore capabilities (51)
read 9
write 5
other 11
Showing 25 of 51
Showing 25 of 51 tools from the public preview. Connect the server to inspect the full live tool list.
Get5
Edit4
Search4
Create3
Other capabilities9
Search Help
read
search_help
Search the global published Help corpus. Returns canonical Help node identifiers and slugs with titles, snippets, and lexical ranking metadata.
Search Help — Search the global published Help corpus. Returns canonical Help node identifiers and slugs with titles, snippets, and lexical ranking metadata.
Get Help Node — Open one canonical published Help node by UUID or full slug path. Returns its Markdown body and ordered preset or DSL demo attachments.
Unified Search — Search across content types (tasks, design docs, plans, and messages) in a project. Returns ranked results with relevance scores and text snippets for context. Provide EITHER `query` (a single search, returning a flat { results, total, hasMore }) OR `queries` (a batch of up to 5 searches run in one call, returning { groups } — one ordered group per input query so you can correlate results back to the query that produced them). Exactly one of `query`/`queries` is required. Use `queries` to fan ou
Task Search — Search for tasks within a project with optional filtering by status, priority, and initiative. Returns tasks ranked by relevance with content snippets.
Search Features — Search for FEATURE-type tasks within a project. Pre-filters to features only — callers never need to specify task type. Supports optional filtering by status, priority, and initiative. Returns features ranked by relevance with content snippets.
Search Goals — Search for GOAL-type tasks within a project. Pre-filters to goals only — callers never need to specify task type. Supports optional filtering by status, priority, and initiative. Returns goals ranked by relevance with content snippets.
Plan Search — Search for plans within a project with optional filtering by status and owner. Returns plans ranked by relevance with content snippets and plan metadata.
Search Design Docs — Search for design documents (ADRs, decisions, brainstorms, plan documents) within a project. Supports filtering by template type, lifecycle status, and tags. Returns documents ranked by relevance with content excerpts.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
heyhey is an MCP server at heyhey.dev. MCPBundles discovered 51 tools on the live endpoint.
How do I connect heyhey to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does heyhey provide?
Operate this server?
Request removal if you do not want heyhey listed here, or claim the listing if you want to manage it on MCPBundles.
Operate heyhey?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Create Work Item — Propose a CREATE proposal for a work item of any type (STANDARD, FEATURE, GOAL, BUG, CONTRACT, DIAGRAM, DIAGRAM_ELEMENT, TASK_MONITOR, or project-defined custom types). Per-type rules — allowed sections, required fields, parentage, the feature-only tag, and Diagram graph payloads — are enforced from the central work-item type config. See get_tool_guidance({ toolName: "create_work_item", workItemType }) for the authoring conventions of the type you are creating. serviceIds is accepted when the pr
Edit Work Item — Propose an UPDATE proposal for a work item of any type. The target's type is resolved server-side and that type's update rules — allowed sections, settable fields — are applied from the central work-item type config. See get_tool_guidance({ toolName: "edit_work_item", workItemType }) for the authoring conventions. For an effective type with registry role `work-item` (normally `STANDARD` or `BUG`), apply status-aware safety only to section content that records what the work does or did: check sta
Edit Tasks — Propose a batch of UPDATE proposals for tasks. See get_tool_guidance({ toolName: "edit_work_item" }) for the authoring conventions — the per-task discipline applies to every edit in the batch. For an effective type with registry role `work-item` (normally `STANDARD` or `BUG`), apply status-aware safety only to section content that records what the work does or did: check status before editing sections. serviceIds is accepted for entries whose project-effective type has registry role "work-item"
Create Design Doc — Propose a CREATE proposal for a BRAINSTORM design document. See get_tool_guidance({ toolName: "create_design_doc" }) for the authoring conventions.
Edit Design Doc — Propose an UPDATE proposal for a design document. See get_tool_guidance({ toolName: "edit_design_doc" }) for the authoring conventions.
Update Proposal — Update an existing proposal record. Use this to modify the proposed changes (updates), influences, or version metadata of a proposal that is still in DRAFT state. Cannot update proposals that have already been APPROVED or REJECTED.
Delete Proposal — Delete an existing proposal record by ID. The deletion is scoped to the authenticated organization and project and reuses the API proposal lifecycle safeguards. This removes the proposal record; it does not approve or enact an entity DELETE proposal.
Get Proposal — Fetch the current state of a proposal by ID. Returns status, action, targetEntityType, targetEntityId, conversationId, and timestamps. Use this to resolve a proposal handle to the real materialized entity ID once the proposal has been APPROVED — the proposal's targetEntityId is rewritten at enactment time to match the entity actually created. Works for DRAFT, APPROVED, and REJECTED proposals.
Start Proposal Group — Start one explicit hidden BUILDING proposal group. Returns the stable group identity and persisted empty authoring snapshot. For the first grouped mutation, pass the returned currentRevision as groupContext.expectedRevision. Membership is never inferred.
Get Proposal Group Authoring Snapshot — Read the persisted BUILDING authoring snapshot for one explicitly identified proposal group. Call this after drafting and dependency changes and immediately before finalization, then pass its currentRevision as groupContext.expectedRevision.
Replace Proposal Group Prerequisites — Replace one member's complete all-of prerequisite set. Pass the latest snapshot currentRevision as groupContext.expectedRevision; prerequisites must be members of that same group.
Remove Proposal Group Member — Remove one persisted member from an explicitly identified BUILDING group. Pass the latest snapshot currentRevision as groupContext.expectedRevision.
Finalize Proposal Group — Validate and atomically freeze the explicitly identified persisted BUILDING revision for review. Pass the immediately preceding authoring snapshot currentRevision as groupContext.expectedRevision. Validation failures return every field-addressable issue and leave the group hidden and mutable.
Create Work Item Type — Propose a new custom work-item type for user review. Before authoring the definition, call get_tool_guidance({ toolName: "create_work_item_type" }) for the canonical review questionnaire and complete configuration contract. Creation requires one completed review of every question.
Edit Work Item Type — After calling get_work_item_type, propose a bounded edit to an active project-owned work-item type (CANONICAL, CANONICAL_OVERRIDE, or PROJECT_CUSTOM). Submit the complete definition and preserve every unchanged definition axis for user review. For a canonical-seeded type, approval creates or updates a complete project override over the immutable global canonical definition; it does not mutate the global seed. List work-item type keys such as STANDARD in allowedParentTypes. When this list is non-
Get Work Item Type Guidance — Read the project-effective semantic guide for a work-item type, with only contexts matching an optional focal type. Use get_work_item_type for the complete administrative definition.
Get Work Item Type — Read the complete project-effective work-item type summary before editing it. Use the returned definition as the base for a read-modify-submit edit.
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 51 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does heyhey require?
heyhey may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.