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

feat: implement current developer system as a separate mcp server #514

Merged
merged 9 commits into from
Dec 30, 2024

Conversation

salman1993
Copy link
Collaborator

@salman1993 salman1993 commented Dec 20, 2024

this is still not complete. the tools are working. resource is not working because i think its currently implemented as a static resource but we might need a resource template (dynamic) - not sure yet

tested with MCP inspector:

npx @modelcontextprotocol/inspector cargo run -p developer

✅ tools
Screenshot 2024-12-20 at 4 31 54 PM

Screenshot 2024-12-20 at 4 31 31 PM

✅ resources
Screenshot 2024-12-23 at 12 26 52 PM

* origin/v1.0:
  Adds 'instructions' field to InitializeResult (#511)
@michaelneale
Copy link
Collaborator

this is very cool - and does make me think - do we want a way to run in-process systems for things are are pretty much always bundled? (but still be a system which could be used out of process)

@salman1993 salman1993 requested a review from wendytang December 23, 2024 18:30
Copy link
Collaborator

@baxen baxen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -0,0 +1,69 @@
use mcp_core::handler::{ResourceError, ToolError};
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like file this should maybe be part of more central library? but i guess reasonable to wait until we have another (although @michaelneale has a new system that would need these i think)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually after reading, maybe we remove this entirely and only use ToolError from mcp_core

self.map_agent_result_to_value(result)
}

// Convert AgentResult<Vec<Content>> to Result<Value, ToolError>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: i haven't thought about it too hard, but might be better to just rework the old code a bit to create ToolError?

@salman1993 salman1993 changed the base branch from v1.0 to v1.0-mcp December 30, 2024 22:24
@salman1993 salman1993 changed the title [draft] feat: implement current developer system as a separate mcp server feat: implement current developer system as a separate mcp server Dec 30, 2024
@salman1993 salman1993 merged commit 1ae75cf into v1.0-mcp Dec 30, 2024
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.

3 participants