Skip to content

♻️ Migrate MCP server to rmcp framework#87

Merged
renardeinside merged 9 commits intomainfrom
feat/decouple-mcp
Feb 18, 2026
Merged

♻️ Migrate MCP server to rmcp framework#87
renardeinside merged 9 commits intomainfrom
feat/decouple-mcp

Conversation

@renardeinside
Copy link
Copy Markdown
Collaborator

Summary

  • Migrate from hand-rolled MCP server to the rmcp framework — replaces custom JSON-RPC transport, message parsing, and routing with rmcp's #[tool_router] / #[tool_handler] macros and stdio transport
  • Restructure monolithic core.rs into modular filescontext.rs, indexing.rs, info_content.rs, resources.rs, validation.rs, and tools/ submodules (databricks, devserver, docs, project, registry)
  • Code quality cleanup — deduplicate AppPathArgs, use rmcp's native structured_error(), fix server name reporting ("apx" instead of "apx-mcp"), add missing read_only_hint annotation on databricks_apps_logs, remove unused reqwest dependency, canonicalize validated paths, add validation tests, add explicit shutdown signaling for background tasks

Test plan

  • cargo build -p apx-mcp — compiles cleanly
  • cargo test -p apx-mcp — all 15 tests pass (including 4 new validation tests)
  • cargo clippy -p apx-mcp — no warnings
  • cargo build — full workspace builds

🤖 Generated with Claude Code

@renardeinside renardeinside merged commit 58728d3 into main Feb 18, 2026
3 checks passed
@renardeinside renardeinside deleted the feat/decouple-mcp branch February 18, 2026 00:51
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.

🗡️ [FEAT] centralize the mcp tooling to avoid per-project mcp installations

1 participant