Cline MCP Server

Created By
mows21a year ago
Cline MCP Server - Internal workflow orchestration for agentic tasks
Overview

what is Cline MCP Server?

Cline MCP Server is an internal workflow orchestration server designed for executing agentic tasks efficiently.

how to use Cline MCP Server?

To use Cline MCP Server, install the necessary dependencies, build the project, and start the server. You can also run it using Docker for easier deployment.

key features of Cline MCP Server?

  • Internal workflow orchestration for agentic tasks
  • API endpoints for agent execution, workflow management, and memory operations
  • Compatibility with JSON-RPC communication for seamless integration

use cases of Cline MCP Server?

  1. Automating daily summary tasks from call notes.
  2. Managing workflows triggered by external tools like n8n.
  3. Executing system commands and managing memory operations.

FAQ from Cline MCP Server?

  • What programming language is Cline MCP Server built with?

Cline MCP Server is built using Python.

  • Is there a Docker version available?

Yes! You can build and run Cline MCP Server using Docker.

  • How can I configure the server?

Configuration can be done through a JSON file specifying the database, port, and authentication token.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mows21
Star
0
Language
Python
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)

4 hours ago
Gpt Scrambler

a day ago