RobotFrameworkLibrary-to-MCP

Created By
noubara year ago
How to turn any robot framework library to a mcp server
Overview

What is RobotFrameworkLibrary-to-MCP?

RobotFrameworkLibrary-to-MCP is a project that enables users to convert any Robot Framework library into an MCP (Multi-Client Protocol) server, allowing for enhanced automation capabilities.

How to use RobotFrameworkLibrary-to-MCP?

To use this project, clone your Robot Framework library, modify the __init__.py file to include a to_mcp function, and run the server using a Python script. You can then connect to the MCP server using any MCP client.

Key features of RobotFrameworkLibrary-to-MCP?

  • Converts Robot Framework libraries into MCP servers.
  • Supports dynamic and hybrid core libraries.
  • Easy integration with MCP clients like VSCode.

Use cases of RobotFrameworkLibrary-to-MCP?

  1. Automating testing processes with Robot Framework libraries.
  2. Integrating various automation tools into a single MCP server.
  3. Enhancing collaboration between different automation clients.

FAQ from RobotFrameworkLibrary-to-MCP?

  • Can I use any Robot Framework library with this project?

Yes! Any Robot Framework library can be converted into an MCP server using this method.

  • Is there a demo available?

Yes! A demo using the MailClientLibrary is documented in the project.

  • What programming language is used?

The project is implemented in Python.

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