Skip to content

MCP post: InvokeServer explanation and connection wording fix#277

Open
ChrisGarty wants to merge 3 commits into
mainfrom
fix/mcp-post-connection-wording
Open

MCP post: InvokeServer explanation and connection wording fix#277
ChrisGarty wants to merge 3 commits into
mainfrom
fix/mcp-post-connection-wording

Conversation

@ChrisGarty
Copy link
Copy Markdown
Contributor

@ChrisGarty ChrisGarty commented Apr 21, 2026

Summary

  • Added explanation of the InvokeServer action in the custom connector (Streamable HTTP POST, JSON-RPC payload). Customer requested more detail on this piece.
  • Clarified that connection creation is prompted during pipeline deployment or solution import (not a separate manual step).
  • Added known limitation callout about putting custom connectors in a solution that is deployed beforehand. Jaime Sicre reminded me about that limitation bullet I wrote a 2-3 years ago!

ChrisGarty and others added 2 commits April 20, 2026 23:59
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Explain the InvokeServer action in the custom connector (Streamable HTTP POST, JSON-RPC payload)
- Clarify that connection creation is prompted during pipeline deployment or solution import

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant