Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prompt messages disparity between MCP and Claude API #151

Open
headinthebox opened this issue Jan 24, 2025 · 0 comments
Open

Prompt messages disparity between MCP and Claude API #151

headinthebox opened this issue Jan 24, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@headinthebox
Copy link

Prompts in MCP represent named parameterized message sequences, that enable reuse by invoking them with concrete arguments.

Currently however, the structure of messages in MCP is not the same as that of messages in the Claude API.

  • The structure of ImageContent is different in MCP and Claude (has an extra "source" wrapper)
  • The structure of TextContent is different in MCP and Claude (has "citations")
  • The Claude API also has "tool_use", "tool_result" which are not present in MCP.
  • The "resource" message type in MCP and new "document" type in the Claude API serve similar purposes.

These differences make it impossible to take an arbitrary Claude prompt sequence and expose it in MCP, or take an MCP prompt sequence and pass it to the Claude API.

I think that MCP and the Claude API should use exactly the same structure for messages.

@headinthebox headinthebox added the enhancement New feature or request label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant