🚀 deco.host — Instant MCP Server Deployment

Created By
deco-cxa year ago
Open-source MCP server platform. A web Ninite for composing your custom MCP server and deploying anywhere.
Overview

What is deco.host?

Deco.host is an open-source platform that allows users to deploy a fully configured Model Context Protocol (MCP) server in seconds, simplifying the management of data sources and integrations for AI agents.

How to use deco.host?

To use deco.host, sign up and log in at deco.host, select your desired data sources from the catalog, and deploy your MCP server with a single click. Share the generated URL with your AI agents to start using it.

Key features of deco.host?

  • Instant one-click MCP server deployment
  • Centralized management of credentials and tools
  • Real-time monitoring and analytics
  • Secure and scalable architecture
  • Seamless integration with deco.chat and other AI tools

Use cases of deco.host?

  1. Rapid deployment of MCP servers for AI applications.
  2. Centralized management of multiple data sources for enterprise solutions.
  3. Integration of internal tools and APIs for enhanced AI functionalities.

FAQ from deco.host?

  • Is deco.host free to use?

Yes, deco.host is open-source and free to use.

  • Can I integrate my existing tools with deco.host?

Yes, deco.host supports integration with various internal tools and APIs.

  • How secure is deco.host?

Deco.host is designed with enterprise-grade security to protect your data and integrations.

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

20 hours ago
Gpt Scrambler

2 days ago