docs: add Agent Guild MCP integration - #597
Draft
AgentTanuki wants to merge 1 commit into
Draft
Conversation
|
@AgentTanuki is attempting to deploy a commit to the deepset Team on Vercel. A member of the Team first needs to authorize it. |
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.
Adds Agent Guild as a community Tool Integration using Haystack's existing
mcp-haystackclient. The page shows how to inspect a public agent endpoint before delegation and retrieve current trust-operation prices, both through direct calls and a Haystack Agent.The examples filter the remote MCP toolset to
guild_preflightandguild_paid_operations. Both calls are free; registration, payment, and paid trust-read tools are excluded. The page explains endpoint data handling, model costs, evidence limits, and source licensing.This follows the README's invitation to contribute an integration page and the hosted-service approach used by the existing Unstructured Transform MCP and Prior Labs entries. It uses published
haystack-ai==3.1.1,mcp-haystack==1.5.1, andmcp==2.2.0, with no separate Agent Guild package.Validation: all 3 local checks passed. The exact Python examples were executed against a loopback Streamable HTTP fixture using the published packages. The checks covered frontmatter/logo, discovery of only the two selected tools, direct calls and result fields, and the native Haystack Agent tool loop with deterministic model responses. No Agent Guild production calls, model-provider calls, registration, or payments were made. The full Haystack site also built locally with Hugo 0.155.2 (508 pages). Browser checks verified the page, logo, all four complete code blocks, six contents links, navigation, and the single Agent Guild result in catalog search. The upstream Vercel preview awaits team authorization.
Files:
integrations/agent-guild.md,logos/agent-guild.svg.