rest-to-mcp

Created By
gavinlinasda year ago
Tutorial project to convert Rest API to an MCP server
Overview

what is rest-to-mcp?

rest-to-mcp is a tutorial project designed to guide users in converting a REST API into an MCP (Microservices Communication Protocol) server.

how to use rest-to-mcp?

To use rest-to-mcp, follow the step-by-step instructions provided in the tutorial available on the GitHub repository. Users will need to have a basic understanding of REST APIs and server configurations.

key features of rest-to-mcp?

  • Comprehensive tutorial for converting REST APIs to MCP servers
  • Step-by-step guidance for implementation
  • Open-source project with MIT license

use cases of rest-to-mcp?

  1. Developers looking to integrate REST APIs with microservices architecture.
  2. Learning resource for understanding MCP server setups.
  3. Reference for building scalable server applications.

FAQ from rest-to-mcp?

  • Is this project suitable for beginners?

Yes! The tutorial is designed to be beginner-friendly, providing clear instructions.

  • What technologies are required to use this project?

Basic knowledge of REST APIs and familiarity with server environments are recommended.

  • Is rest-to-mcp open-source?

Yes! The project is open-source and licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gavinlinasd
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