Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Myoutfitters is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search Canadian hunting and fishing outfitters, check availability, and send price requests.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http myoutfitters-mcp https://myoutfitters.ca/mcp
# 2 — ask your agent for something these tools do
# list_reference_data, search, fetch and 5 more
Myoutfitters costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MYAll 1 server
myoutfitters1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http myoutfitters-mcp https://myoutfitters.ca/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List the values MyOutfitters understands for each search filter: provinces, regions, species, activity types, meal plan types, lodging types, access types, amenities, ZECs, major cities used as driving origins, and seasons. Contains no outfitter data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | — |
| province | string | no | Filter regions, ZECs or cities by province. |
| locale | string | no | — |
| api_key | string | no | — |
Free-text search over MyOutfitters' Canadian hunting and fishing outfitters (pourvoiries). Returns up to 10 documents with id, title and URL; pass an id to fetch for the full profile. For precise multi-criteria filtering (species, region, budget, lodging, dates) prefer search_outfitters. No phone, e-mail or website is ever returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Natural-language query, e.g. 'white pike fishing in Lanaudière' or 'pourvoirie chasse orignal Abitibi'. |
| limit | integer | no | — |
| locale | string | no | — |
| api_key | string | no | — |
Retrieve one MyOutfitters outfitter document by the id returned by search (e.g. 'PV-0009') or by its MyOutfitters URL. Returns id, title, url, readable text and metadata. No phone, e-mail or website is ever returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document id from search (e.g. 'PV-0009') or the outfitter's MyOutfitters URL. |
| locale | string | no | — |
| api_key | string | no | — |
Find up to 10 Canadian hunting and fishing outfitters (pourvoiries) matching a traveller's criteria, using the same advanced filters as the website: activities, several species at once, province, region, ZEC, access type, driving distance from a major city, Collection Prestige, per-person nightly budget, lodging type, single-lodging capacity, bedrooms, two-person and one-person bed counts, meal pl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| province | string | no | Province code or name, e.g. 'QC', 'Ontario'. |
| region | string | no | A single tourist region, e.g. 'Mauricie'. |
| regions | array | no | Several tourist regions; an outfitter matches any of them. |
| zecs | array | no | ZEC names (Quebec controlled-exploitation zones). |
| near_city | string | no | Major city used as the driving origin, e.g. 'Montréal', 'Toronto'. |
| max_drive_hours | number | no | Maximum driving hours from near_city (requires near_city). |
| activity | string | no | Shorthand for the two main activities. |
| activities | array | no | Exact activity-type codes an outfitter must offer: chasse (hunting), peche (fishing), big_game_hunting, ice_fishing (pêche sur glace), bird_hunting (chasse aux oiseaux), nature_lodging, family_experie |
| species | no | One species or several, e.g. ['doré','brochet'] / ['walleye','pike']. | |
| species_match | string | no | 'all' (default) requires every species; 'any' matches at least one. |
| hunt_or_fish_keyword | string | no | Deprecated alias of keyword. |
| keyword | string | no | Free text matched against the outfitter name, town, street address and the lakes, reservoirs and rivers it operates on; water-body and address matches rank first. |
| party_size | integer | no | Number of guests to accommodate. |
| min_bedrooms | integer | no | Minimum bedrooms in a single lodging ('minimum 4 chambres' / '4 rooms'). |
| min_double_beds | integer | no | Minimum number of two-person beds in that SAME lodging (double, queen, king; a double bunk bed counts as 2). |
| min_single_beds | integer | no | Minimum number of one-person beds in that SAME lodging (single beds; a bunk bed counts as 2). |
| min_lodging_capacity | integer | no | Minimum number of people a SINGLE cabin/lodging must sleep (e.g. 'a cabin for 10 people' → 10). Different from party_size, which is how many travellers are coming. |
| max_price_per_person | number | no | Cap on the starting package price per person. |
| budget_min_per_person_night | number | no | — |
| budget_max_per_person_night | number | no | Cap on the per-person, per-night rate (package price divided by nights). |
Public profile of one outfitter: territory, species, season, and up to 8 summarised packages. Rates appear only when the outfitter has confirmed its listing. No phone, e-mail or website is ever returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outfitter_id | string | yes | Outfitter id (e.g. 'PV-0009') or the id-bearing URL segment. |
| locale | string | no | — |
| api_key | string | no | — |
For one outfitter, return how a stay can be booked: booking mode (online payment on MyOutfitters, or a price request through MyOutfitters' anonymised relay), the packages that fit the party and the requested dates, indicative per-person rates when the listing is confirmed, the season window and the exact next step. Optionally pass dates and party size to filter the packages and get a season/availa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outfitter_id | string | yes | Outfitter id (e.g. 'PV-0009') or the id-bearing MyOutfitters URL segment. |
| arrival | string | no | Requested arrival date (YYYY-MM-DD). |
| departure | string | no | Requested departure date (YYYY-MM-DD). |
| party_size | integer | no | — |
| locale | string | no | — |
| api_key | string | no | — |
For up to 10 named outfitters, tell whether the requested dates fall in season and which packages fit the party. Returns a verdict per outfitter, never raw inventory.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outfitter_ids | array | yes | Outfitter ids obtained from search_outfitters. |
| arrival | string | yes | — |
| departure | string | yes | — |
| party_size | integer | no | — |
| locale | string | no | — |
| api_key | string | no | — |
Send a traveller's enquiry to one outfitter through MyOutfitters' anonymised relay. Requires the traveller's own name and e-mail, given with their consent. The outfitter replies by e-mail; neither side sees the other's raw contact details.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outfitter_id | string | yes | — |
| full_name | string | yes | — |
| string | yes | — | |
| phone | string | no | — |
| message | string | yes | — |
| arrival | string | no | — |
| departure | string | no | — |
| party_size | integer | no | — |
| package_id | string | no | — |
| locale | string | no | — |
| api_key | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Myoutfitters or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Myoutfitters can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.