Repository navigation
Conversation
Collaborator
|
Thanks for putting this together. We keep the examples focused on dynamiq features rather than specific third-party services, and connecting to an MCP server is already covered by the existing |
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 a separate opt-in example that publishes an HTML page to a public
https://{slug}.deed.page/URL through Dynamiq's existingMCPServerandMCPStreamableHTTPadapter, then deletes it again. Runpython -m examples.components.tools.mcp_server_as_tool.use_deed_pagefrom the repository environment. It publishes a small sample page that expires after an hour. Pass--file report.html,--slugor--ttl 0to publish your own page or keep it.The example limits the server to
publish_siteanddelete_sitewithinclude_tools. It uses no LLM, API key or account and sends no Authorization header. The first publish returns an owner token.--delete <slug>reads it fromDEEDPAGE_TOKENand exits with a clear message if it isn't set. The adjacent README has the install command, the run and delete commands, and a note that published pages are public. Existing examples and provider defaults are unchanged.Validated the documented Python 3.12 install and each documented command against the live endpoint. The sample page loaded. Delete without the token failed with the expected message, and with the token it removed the page, which then returned 404. Upstream pre-commit hooks pass on the changed files, plus
ruff checkandblack --check -l 120. I didn't run the full test suite, since only an example and its README change.The branch has two commits. The second only renames the token variable to
DEEDPAGE_TOKEN, so it squashes cleanly.I'm on the deed.page team (Avatar 8 LLC), which runs this MCP server. Docs: https://deed.page/docs. Agent skill (MIT): https://github.com/f-o-x11/deed-page-skill