mcp-agent-tool-adapter

Created By
serkanyasra year ago
Transforms MCP tools into collaborative, reasoning agents using modern agent frameworks.
Overview

What is MCP Agent Tool Adapter?

MCP Agent Tool Adapter transforms MCP tools into collaborative, reasoning agents using modern agent frameworks, enabling modular tool invocation via the MCP protocol.

How to use MCP Agent Tool Adapter?

To use the MCP Agent Tool Adapter, clone the repository, install the dependencies, and run either the Google ADK CLI agent or the LangGraph ReAct CLI agent as per your requirements.

Key features of MCP Agent Tool Adapter?

  • Modular tool invocation through the MCP protocol.
  • Supports Google ADK-based agents with streaming FastAPI or CLI interfaces.
  • LangGraph-based agents that utilize ReAct + streaming tool planning.

Use cases of MCP Agent Tool Adapter?

  1. Creating intelligent agents that can reason with various tools.
  2. Developing modular applications that require dynamic tool invocation.
  3. Enhancing collaborative workflows with automated reasoning capabilities.

FAQ from MCP Agent Tool Adapter?

  • What programming language is used?

The project is developed in Python.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • How can I contribute to the project?

You can fork the repository, create feature branches, and submit a PR with your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
serkanyasr
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago