LuuphubDOCSDashboard
[00]AUTOMATE / MCP /

MCP server

Luuphub ships a remote Model Context Protocol server so an AI agent (Claude Code, Cursor, the MCP Inspector) can read and triage feedback over the same scoped API keys, tenant isolation, and audit log as the REST API.

Endpoint

https://app.luuphub.com/api/mcp/mcp

Streamable HTTP transport. Authenticate with an API key as a bearer token: Authorization: Bearer lh_live_…. Keys are created in the dashboard under Developers. API access requires a Pro plan or higher.

Scopes & the site restriction

A tool runs only if the key carries the tool's scope. New keys are read-onlyby default — the write tools below need explicit write scopes. If a key is restricted to a single site, any tool argument naming a different site is rejected (403), never silently re-scoped. The key's scope and site restriction — not tool arguments — decide what it can reach.

Read tools

Available on the default read-only key.

TOOLREQUIRED SCOPEMIRRORS API OPERATION
list_sitessites:readlistSites
get_sitesites:readgetSite
list_boardsboards:readlistBoards
list_postsposts:readlistPosts
get_postposts:readgetPost
search_postssearch:readsearchPosts
list_commentscomments:readlistComments
list_statusesstatuses:readlistStatuses
list_changelogchangelog:readlistChangelog
get_insightsinsights:readgetInsights
get_autopilot_queueautomation:readgetAutopilotQueue

Write tools

Destructive / mutating. Require the listed write scope. Every call appends an audit entry attributed to agent:<keyId>, and a merge is one-click reversible from the dashboard.

TOOLREQUIRED SCOPEMIRRORS API OPERATION
create_postposts:writecreatePost
reply_to_postcomments:writecreateComment
change_post_statusstatuses:writechangePostStatus
create_boardboards:writecreateBoard
create_statusstatuses:writecreateStatus
vote_on_postvotes:writecreateVote
merge_postsposts:writemergePosts
start_agent_runautomation:writestartAgentRun
append_run_stepautomation:writeappendAgentRunStep
complete_agent_runautomation:writecompleteAgentRun

Trust model

  • Tool output that carries visitor-authored text (post/comment bodies, insight summaries) is wrapped as untrusted — treat it as data, not instructions.
  • Every mutation is logged to the AI action audit with the calling key's identity; destructive actions can be undone from the dashboard.
  • AI-powered tools (semantic search_posts) consume your account AI budget and soft-fail with an upgrade prompt when exhausted.