boamp-server MCP Server

Created By
stefwa year ago
Serveur MCP (Model Context Protocol) pour interroger l'API BOAMP et récupérer les avis de marchés publics. Ce serveur permet de rechercher des marchés publics en utilisant divers critères et d'obtenir des détails complets sur des marchés spécifiques.
Overview

what is boamp-server?

boamp-server is a Model Context Protocol (MCP) server designed to query the BOAMP API and retrieve public market notices. This server allows users to search for public markets using various criteria and obtain complete details about specific markets.

how to use boamp-server?

To use boamp-server, install the necessary dependencies, build the server, and configure it with Claude Desktop. You can then query public markets by sending requests with specific parameters.

key features of boamp-server?

  • Retrieve public market notices based on keywords and other criteria.
  • Get complete details of specific markets.
  • Supports various market types (SERVICES, WORKS, SUPPLIES).

use cases of boamp-server?

  1. Searching for public markets containing specific keywords like "communication" and "digital".
  2. Retrieving details of a specific market using its ID.
  3. Exporting search results into a CSV format for analysis.

FAQ from boamp-server?

  • What types of markets can I search for?

You can search for various types of markets including services, works, and supplies.

  • How do I install boamp-server?

Install dependencies using npm install, build the server with npm run build, and configure it for use with Claude Desktop.

  • Can I debug the server?

Yes, you can use the MCP Inspector for debugging, which provides a URL to access debugging tools in your browser.

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