🐶 AppDog: Effortless MCP Server Generation

Created By
Arya711139a year ago
Compose and generate effortlessly MCP servers from any OpenAPI specifications
Overview

What is AppDog?

AppDog is a tool designed to effortlessly compose and generate Model Context Protocol (MCP) servers from any OpenAPI specifications, streamlining the development process for API developers.

How to use AppDog?

To use AppDog, clone the repository, install the necessary dependencies, and run the application. You can generate an MCP server by providing an OpenAPI specification file and executing simple commands.

Key features of AppDog?

  • Seamless integration with OpenAPI specifications for server generation.
  • Fast and efficient server setups.
  • Asynchronous support for handling multiple requests.
  • Easy-to-use command-line interface.
  • Built with Python for robust API development.

Use cases of AppDog?

  1. Quickly generating MCP servers for new API projects.
  2. Simplifying the setup process for developers working with OpenAPI.
  3. Enhancing productivity by automating server generation tasks.

FAQ from AppDog?

  • What programming language is AppDog built with?

AppDog is built using Python.

  • Can I contribute to AppDog?

Yes! Contributions are welcome. Please follow the contribution guidelines in the repository.

  • Is there documentation available?

Yes, comprehensive documentation is available on the project's Wiki page.

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