Code2Flow MCP 服务器

Created By
kursk-yea year ago
Code2Flow MCP服务器,用于生成代码调用图并通过MCP协议提供服务
Overview

what is Code2Flow MCP Server?

Code2Flow MCP Server is a project that wraps the code2flow command-line tool into an MCP (Model Context Protocol) server, allowing AI applications to generate and access code call graphs through a standardized MCP protocol.

how to use Code2Flow MCP Server?

To use the Code2Flow MCP Server, clone the repository, set up a virtual environment, install dependencies, and run the server using Python. You can also use MCP tools to interact with the server.

key features of Code2Flow MCP Server?

  • Analyzes source code and generates call graphs
  • Supports multiple programming languages (Python, JavaScript, Ruby, PHP)
  • Provides services via MCP protocol for easy integration with AI applications
  • Outputs images in PNG format
  • Includes version checking and code complexity analysis features

use cases of Code2Flow MCP Server?

  1. Generating call graphs for codebases in various programming languages.
  2. Analyzing code complexity to improve code quality.
  3. Integrating with AI applications for enhanced code understanding.

FAQ from Code2Flow MCP Server?

  • What programming languages does Code2Flow MCP Server support?

It supports Python, JavaScript, Ruby, and PHP.

  • How do I install Code2Flow MCP Server?

Clone the repository, create a virtual environment, install dependencies, and run the server.

  • Can I use it with AI applications?

Yes! It is designed for easy integration with AI applications through the MCP protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kursk-ye
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago