feat(simple-mcp): use visitor API integration; also add stateless_http#312
feat(simple-mcp): use visitor API integration; also add stateless_http#312nealrichardson merged 5 commits intomainfrom
Conversation
|
I am unable to test the visitor api key logic successfully. If i remove the integration and restart the process I am not seeing anything notifying the user to add one. |
Come to think of it, I didn't see anything either, I just knew I needed to add it so I did. Want me to remove it or fix it or what? |
|
Could be a follow up issue unless you have time to mess with it now. What I think may be more important is expanding the description text to include a lot of what you have for the zendesk mcp server i.e. auth details (basic api key auth not oauth2.1) |
mconflitti-pbc
left a comment
mconflitti-pbc
left a comment
There was a problem hiding this comment.
other than making the description better, tested and working as expected
- Remove /api/visitor-auth and /api/integrations endpoints - Remove JS-based integration status checking from landing page - Add static info box documenting Visitor API Key requirement - Add setup instructions for Claude Code, Claude Desktop, VS Code, Cursor Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Use native VS Code mcp.json format instead of Continue extension format. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Matt Conflitti <matt.conflitti@posit.co>
|
I've adjusted the landing page, want to have another look? |
mconflitti-pbc
left a comment
mconflitti-pbc
left a comment
There was a problem hiding this comment.
looks good. only nit is to have each tool: claude, cursor, etc be collapsible/expandable
Use HTML <details> elements to make Claude Code, Claude Desktop, VS Code, and Cursor setup instructions collapsible for cleaner UI. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2 participants
Fixes #311
Fixes #298
Claude also added helpers to guide the user to add the integration if it is not set, I believe cribbing off the publisher command center. Not sure if we want to keep that or not--kinda belies the "simple" MCP server, and also do we not have ways to automatically associate integrations now?
I confirmed this works and that users of the MCP server don't have to set any custom headers to get the
whoamitool to work now.