Draft
Conversation
afsalthaj
commented
Feb 24, 2026
| environment_id UUID NOT NULL, | ||
| deployment_revision_id BIGINT NOT NULL, | ||
| domain TEXT NOT NULL, | ||
| agent_type_implementers TEXT NOT NULL, |
Contributor
Author
There was a problem hiding this comment.
Will change this.
Contributor
Author
|
The way we are going to write integration test is as follows: Initializationcurl -i -X POST https://restaurant-hamburg-sims-los.trycloudflare.com/mcp \
-H "Content-Type: application/json, text/event-stream" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2024-11-05",
"capabilities": {},
"clientInfo": {
"name": "curl-client",
"version": "1.0.0"
}
}
}'Inititalized Notification requestcurl -i -X POST https://restaurant-hamburg-sims-los.trycloudflare.com/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Mcp-Session-Id: 20718598-6ac9-4503-a683-80e999db5044" \
-d '{
"jsonrpc": "2.0",
"method": "notifications/initialized",
"params": {}
}'And finally, a simple tool/list callcurl -X POST http://restaurant-hamburg-sims-los.trycloudflare.com/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Mcp-Session-Id: 20718598-6ac9-4503-a683-80e999db5044" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list",
"params": {}
}' |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2792
Bootstrapping MCP server, the flattened version as documented. Need to do a few clean ups before making it ready for review.
I am not making CLI changes in this PR (it's a separate ticket) but whatever that's required for CLI from the server side is done (McpDeploymentClientLive).
However, I added a small to-be-removed snippet to see if this really works with a real AI. And it's confirmed the entire thing to be working with Open AI client: https://platform.openai.com/chat/edit?models=gpt-4.1-mini
Testing with Open AI
golem new, built a new rust agent (see below)The name of the tool is a bit odd, bu I will be fixing it as part of cleaning things up. The above screenshot successfully handshaked with Golem and listed tools
User experience using MCP Server
The actual usage looks very reasonable. The fact that constructor parameters being part of the tool itself seems to be very reasonable as well as flexible.
For example see this specific situation. Here name is a constructor argument
Here I just prompted to increment by 10, but forgot to mention which counter (the value of the constructor param) and client tell us the user to give more details.
Statefulness
The statefulness is about being able to hit the same identity of the agent, that's it.
The agent that was used:
Input Schema and Output Schema and different AI behaviours.
Note that in OpenAI, I couldn't see it really considering output-schema. It did care about input-schema, and I could actually see the final response (json value). This questions whether our output schema works. This may or may not be our problem, and the only way to test this manually doing a handshaking following MCP protocol and see if the response schema is detailed. And for us it works.
See this #2833 (comment)