
Fetchpet
com.pulsemcpPublished by pulsemcp.comv0.1.8Updated Oct 25, 2026
MCP server for Fetch Pet insurance claims management using Playwright automation.
Overview
A local MCP server that drives a logged-in Fetch Pet insurance account through browser automation to prepare and submit claims and retrieve claim details.
- What you can do
- Prepare a claim form with validation, without submitting it, and return a confirmation token for later submission. Submit a prepared claim once the confirmation token is supplied. List all active and historical claims in a single call. Fetch claim details and download EOB and invoice documents to a configured directory.
- When to use it
- Useful for Fetch Pet policyholders who want an assistant to draft and file pet insurance claims, check claim status and history, or pull down EOB and invoice documents without navigating the site by hand.
- Requirements
- Runs locally via npx, so Node.js 18+ is needed. A Fetch Pet account is required, with credentials supplied through the FETCHPET_USERNAME and FETCHPET_PASSWORD environment variables. Optional settings: HEADLESS, TIMEOUT and FETCHPET_DOWNLOAD_DIR. Network access to the Fetch Pet website is required.
Installation
In SourceWeft
- Open Fetchpet in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Fetch Pet MCP Server
MCP server for Fetch Pet insurance claims management using Playwright automation. Submit claims, track claim status, and view claim details including EOB and invoices.
Features
- Prepare Claims - Fill out claim forms with validation (without submitting)
- Submit Claims - Actually submit prepared claims with explicit user confirmation
- View All Claims - See all claims (active and historical) in a single call
- Claim Details - Get detailed information including EOB and invoice downloads
Tools
Setup
Prerequisites
- Node.js 18+
- A Fetch Pet account (create one at fetchpet.com)
Environment Variables
Claude Desktop
Make sure you have your Fetch Pet account credentials ready.
Then proceed to the setup instructions below. If this is your first time using MCP Servers, you'll want to make sure you have the Claude Desktop application and follow the official MCP setup instructions.
Manual Setup
You're going to need Node working on your machine so you can run npx commands in your terminal. If you don't have Node, you can install it from nodejs.org.
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Modify your claude_desktop_config.json file to add the following:
Restart Claude Desktop and you should be ready to go!
Usage Examples
Submit a new claim
The assistant will:
- Use
prepare_claim_to_submitto fill out the form - Show you exactly what will be submitted
- Ask for your explicit confirmation
- Only then call
submit_claimwith the confirmation token
View claims
Get claim details
How It Works
This MCP server uses Playwright to automate a browser session with Fetch Pet:
- On server start: Launches a browser in the background and logs into your Fetch Pet account
- Browser session persists: All subsequent tool calls reuse the same logged-in session
- Smart navigation: Tools navigate to the appropriate pages as needed
- Stealth mode: Uses playwright-extra with stealth plugin to avoid bot detection
Claim Submission Safety
The claim submission process is designed with safety in mind:
prepare_claim_to_submitfills out the form and validates everything but does NOT click submit- It returns a unique confirmation token
submit_claimrequires this token, ensuring explicit user confirmation- Without the correct token, claims cannot be submitted
Development
Project Structure
Security Notes
- Your Fetch Pet credentials are used only to log into your account
- The browser session runs locally on your machine
- No credentials are transmitted to any third-party services
- Consider using environment variables rather than hardcoding credentials
- Downloaded documents (EOB, invoices) are saved to the configured download directory
Limitations
- Requires a valid Fetch Pet account
- Browser automation may occasionally fail if Fetch Pet updates their website
- Some operations require navigating between pages which takes time
- The website uses a React app, so dynamic content loading may require waits
License
MIT
Source: experimental/fetchpet/README.md at commit 0ed34de
Tools
0Version history
1- v0.1.8LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts