DEMO: dynamic MCP with semantic search tool selection

[ryan-timothy-albert]

THIS IS NOT INTENDED TO BE MERGEABLE

• Any speakeasy toolset can by default expose a find_tools and execute_tool as their only tools in the MCP
• Uses chromem-go as an in memory store to embed tools for later semantic search (openai embeddings)
• The LLM use find_tools to search for relevant tools for its query and execute_tool to execute with arguments.
• A simple header Gram-Dynamic-MCP decides whether or not the MCP should be used in a dynamic context

What this solution is not productionized

• We are embedding on the fly when list tools is called. In reality this would need to be a pre-step
  • Vector DB probably shouldn't just be in memory
• Need someway to keep embeddings in sync with tools in the toolset
• Probably need a way to pre-identify a toolset as Dynamic. Not just completely on the fly via header
• Unclear how well tool selection would work on very large diverse toolsets
  • Perhaps could introduce an LLM pre-step where an LLM produces and optimized description for a tool before embedding. I'm ready some approaches like this

[changeset-bot]

⚠️ No Changeset found

Latest commit: 28abb7f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
gram	Building	Preview	Comment	Nov 10, 2025 8:22pm
gram-docs-redirect	Ready	Preview	Comment	Nov 10, 2025 8:22pm
gram-landing-redirect	Ready	Preview	Comment	Nov 10, 2025 8:22pm