Offorte MCP Server

Created By
offortea year ago
MCP server for the Offorte API - Create & send proposals using AI
Overview

What is Offorte MCP Server?

Offorte MCP Server is a server designed to facilitate the creation and sending of proposals using AI through the Offorte API. It acts as a bridge between AI agents and Offorte's proposal engine, enabling automation workflows for proposal actions.

How to use Offorte MCP Server?

To use the Offorte MCP Server, you need to set up the server with Node.js, obtain an Offorte API key, and configure it according to the provided instructions. You can then utilize various tools to create and send proposals.

Key features of Offorte MCP Server?

  • Integration with Offorte's proposal engine for automated proposal creation.
  • Support for various automation tools to streamline proposal workflows.
  • Voice-triggered and AI-powered proposal sending capabilities.

Use cases of Offorte MCP Server?

  1. Automating the proposal creation process for businesses.
  2. Integrating proposal actions into chat interfaces and AI tools.
  3. Enhancing proposal workflows with voice commands.

FAQ from Offorte MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a new approach to AI integration that allows for automated proposal actions.

  • Is there a demo available?

Yes! You can experience a demo of the Offorte MCP Server in action on their website.

  • What are the prerequisites for using the server?

You need Node.js, an Offorte API key, and PNPM for development.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
offorte
Star
1
Language
TypeScript
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)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago