Search / io.github.AtlasDigitalDesign/intertwine-plans
intertwine-plans
R0· no sign-inSearch Angela Kamer's coastal house plans by beds, sq ft, lot width, pilings and elevator.
v1.2.1 · active · repository · descriptor JSON · versions
Search / io.github.AtlasDigitalDesign/intertwine-plans
R0· no sign-inSearch Angela Kamer's coastal house plans by beds, sq ft, lot width, pilings and elevator.
v1.2.1 · active · repository · descriptor JSON · versions
{
"mcpServers": {
"intertwine-plans": {
"type": "http",
"url": "https://agents.intertwinehouseplans.com/mcp"
}
}
}claude mcp add --transport http intertwine-plans https://agents.intertwinehouseplans.com/mcp[mcp_servers.intertwine-plans]
url = "https://agents.intertwinehouseplans.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"intertwine-plans": {
"type": "remote",
"url": "https://agents.intertwinehouseplans.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"intertwine-plans": {
"type": "http",
"url": "https://agents.intertwinehouseplans.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=intertwine-plans&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYWdlbnRzLmludGVydHdpbmVob3VzZXBsYW5zLmNvbS9tY3AifQ%3D%3D"
}{
"servers": {
"intertwine-plans": {
"type": "http",
"url": "https://agents.intertwinehouseplans.com/mcp"
}
}
}{
"mcpServers": {
"intertwine-plans": {
"httpUrl": "https://agents.intertwinehouseplans.com/mcp"
}
}
}extensions:
"intertwine-plans":
enabled: true
name: "intertwine-plans"
type: streamable_http
uri: "https://agents.intertwinehouseplans.com/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations6 of 6 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 2,447 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changes, stability.rug_pulltool history recorded for 0 of the 7 days neededdeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagebuying_helpchangeddescription, input schema, annotationsmeaning changedAnswers a buyer's questions before purchase: what a plan set includes, study sets, changing a plan, why there is no cost-to-build calculator and how to get a real number, plans that have been built (with photos), and the store's FAQ. Optionally pass words to match FAQ questions.
Answer a buyer's question before purchase using the store's own help pages. Pick one topic: whats_included (what a plan set contains and doesn't), study_sets (the $75 preview set and its credit), modifications (how changes are quoted and requested), cost_to_build (why there is no calculator and how to get a real number), built_homes (plans that have been built, with photos) or faq (the store's live FAQ). For faq, pass `question` to return only entries whose question or answer contains one of its words. Returns { topic, title, page } with the answer text; faq adds questions[] (question and answer pairs) and built_homes adds plans[] in search_plans form. Use get_plan for questions about one plan's specs or price. Read-only.
about_designerchangeddescription, input schema, annotationsmeaning changedWho draws these plans, what plan sets come as, study sets, and how to ask for changes.
Get background on the designer and how buying from her works. Takes no arguments. Returns a fixed summary: designer (Angela Kamer, residential designer), background (training and coastal experience), what the store sells, plan set formats, how $75 study sets work and are credited, how modifications are quoted, the modification request link, the number of plans and the list of buying_help topics. Use this when the buyer asks who drew the plans or how ordering works in general; use buying_help for a specific pre-purchase question and get_plan for a specific plan. Read-only.
list_featureschangeddescription, input schema, annotationsmeaning changedThe styles and features plans are grouped by, with how many plans carry each.
List every style and feature value the catalog uses, with how many plans carry each. Takes no arguments. Returns { totalPlans, features } where features maps each value (for example "elevated coastal": 39, "elevator": 21) to its count across all 68 plan sets; a plan can carry several. Use this to see what the catalog offers before searching, or to pick a valid `feature` value for search_plans. It returns counts only; use search_plans to get the plans themselves. Read-only.
plans_for_lotchangeddescription, input schema, annotationsmeaning changedGiven a lot's width and depth in feet and its setbacks, returns the plans whose footprint fits the buildable area. A first screen only: confirm setbacks, flood zone and local rules with the jurisdiction and the designer.
Find the plans whose house footprint fits a specific lot. Use this when the buyer gives lot width and depth; use search_plans when they only describe the house. Subtracts the setbacks from the lot (side setback from each side, plus front and rear), then returns { buildableArea, matches, plans[], note }: the buildable rectangle, the number of plans that fit, up to `limit` of them largest first with the same fields as search_plans, and a reminder that porches and stairs can extend past the footprint. This is a first screen only. Setbacks, flood zone, height limits and local codes must be confirmed with the jurisdiction and the designer. Read-only.
get_planchangeddescription, input schema, annotationsmeaning changedEverything about one plan, by name, other published name, or handle (for example The Heron or the-heron): specs, footprint, foundation options, garage, ceilings, roof pitch, framing, smallest lot it suits, photos and floor plans, every package with its current and regular price, the full design write-up, the study set link and price, how to request changes, and its page.
Get the complete record for one house plan. Use this after search_plans or plans_for_lot, or when the buyer names a plan. Accepts the plan's name, any other name it is published under, or its URL handle (for example The Heron, Lambert's Cottage or the-heron); matching is case-insensitive, ignores a leading "The" and falls back to a partial name match. Returns specs (bedrooms, baths, heated and total sq ft, stories, width, depth, max ridge height, ceilings, roof pitch, framing, garage, ground level), yes/no flags for elevated, elevator, drive-under, in-law suite and garage ADU, the narrowest lot it suits, foundation options with any added fee, every package (PDF, PDF plus CAD, Chief Architect) with current and regular price, image URLs, the full design write-up, the $75 study set link, the change request link, a built-home link when one exists, other published names and the plan page URL. If no plan matches, it returns an error that says to use search_plans. Read-only.
search_planschangeddescription, input schema, annotationsmeaning changedSearch Intertwine House Plans by the specs a buyer cares about: bedrooms, bathrooms, heated square feet, stories, width and depth, elevated or pilings foundation, elevator, drive-under garage, in-law suite, garage ADU, and style (beach, cottage, Low Country, carriage house). Returns matching plans with key specs, a photo, the current starting price (and sale price when one is running) and the plan's page.
Find house plans in the Intertwine House Plans catalog (68 plan sets by residential designer Angela Kamer) that match a buyer's requirements. Use this first when someone describes the house they want: bedrooms, baths, size, width, an elevated or pilings foundation, an elevator, a drive-under garage, an in-law suite, a garage apartment, a style or a budget. All filters are optional and combine with AND; leave out any the buyer didn't mention. Returns { count, plans[] } where count is the total number of matches and plans holds up to `limit` of them in catalog order, each with name, subtitle, bedrooms (and optional bedrooms), baths, heated sq ft, stories, footprint, foundation, features, starting price (plus the regular price when a sale is on), one photo URL and the plan's page URL. Use get_plan for everything about one plan, plans_for_lot when the buyer gives lot dimensions, and list_features to see which style and feature values exist. Read-only; it never buys or changes anything.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +reachable +uptime-100% +updated-0d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://agents.intertwinehouseplans.com/mcp streamable-http | none | yes | 100% | 153 ms | 2025-11-25 | 2026-11-07 |
about_designerread-only | Get background on the designer and how buying from her works. Takes no arguments. Returns a fixed summary: designer (Angela Kamer, residential designer), background (training and coastal experience), what the store sells, plan set formats, how $75 study sets work and are credited, how modifications are quoted, the modification request link, the number of plans and the list of buying_help topics. Use this when the buyer asks who drew the plans or how ordering works in general; use buying_help for a specific pre-purchase question and get_plan for a specific plan. Read-only. |
buying_helpread-only | Answer a buyer's question before purchase using the store's own help pages. Pick one topic: whats_included (what a plan set contains and doesn't), study_sets (the $75 preview set and its credit), modifications (how changes are quoted and requested), cost_to_build (why there is no calculator and how to get a real number), built_homes (plans that have been built, with photos) or faq (the store's live FAQ). For faq, pass `question` to return only entries whose question or answer contains one of its words. Returns { topic, title, page } with the answer text; faq adds questions[] (question and answer pairs) and built_homes adds plans[] in search_plans form. Use get_plan for questions about one plan's specs or price. Read-only. |
get_planread-only | Get the complete record for one house plan. Use this after search_plans or plans_for_lot, or when the buyer names a plan. Accepts the plan's name, any other name it is published under, or its URL handle (for example The Heron, Lambert's Cottage or the-heron); matching is case-insensitive, ignores a leading "The" and falls back to a partial name match. Returns specs (bedrooms, baths, heated and total sq ft, stories, width, depth, max ridge height, ceilings, roof pitch, framing, garage, ground level), yes/no flags for elevated, elevator, drive-under, in-law suite and garage ADU, the narrowest lot it suits, foundation options with any added fee, every package (PDF, PDF plus CAD, Chief Architect) with current and regular price, image URLs, the full design write-up, the $75 study set link, the change request link, a built-home link when one exists, other published names and the plan page URL. If no plan matches, it returns an error that says to use search_plans. Read-only. |
list_featuresread-only | List every style and feature value the catalog uses, with how many plans carry each. Takes no arguments. Returns { totalPlans, features } where features maps each value (for example "elevated coastal": 39, "elevator": 21) to its count across all 68 plan sets; a plan can carry several. Use this to see what the catalog offers before searching, or to pick a valid `feature` value for search_plans. It returns counts only; use search_plans to get the plans themselves. Read-only. |
plans_for_lotread-only | Find the plans whose house footprint fits a specific lot. Use this when the buyer gives lot width and depth; use search_plans when they only describe the house. Subtracts the setbacks from the lot (side setback from each side, plus front and rear), then returns { buildableArea, matches, plans[], note }: the buildable rectangle, the number of plans that fit, up to `limit` of them largest first with the same fields as search_plans, and a reminder that porches and stairs can extend past the footprint. This is a first screen only. Setbacks, flood zone, height limits and local codes must be confirmed with the jurisdiction and the designer. Read-only. |
search_plansread-only | Find house plans in the Intertwine House Plans catalog (68 plan sets by residential designer Angela Kamer) that match a buyer's requirements. Use this first when someone describes the house they want: bedrooms, baths, size, width, an elevated or pilings foundation, an elevator, a drive-under garage, an in-law suite, a garage apartment, a style or a budget. All filters are optional and combine with AND; leave out any the buyer didn't mention. Returns { count, plans[] } where count is the total number of matches and plans holds up to `limit` of them in catalog order, each with name, subtitle, bedrooms (and optional bedrooms), baths, heated sq ft, stories, footprint, foundation, features, starting price (plus the regular price when a sale is on), one photo URL and the plan's page URL. Use get_plan for everything about one plan, plans_for_lot when the buyer gives lot dimensions, and list_features to see which style and feature values exist. Read-only; it never buys or changes anything. |
Schemas: list_tools.
{
"name": "io.github.AtlasDigitalDesign/intertwine-plans",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
"remotes": [
{
"url": "https://agents.intertwinehouseplans.com/mcp",
"type": "streamable-http"
}
],
"version": "1.2.1",
"repository": {
"url": "https://github.com/AtlasDigitalDesign/intertwine-plans-mcp",
"source": "github"
},
"description": "Search Angela Kamer's coastal house plans by beds, sq ft, lot width, pilings and elevator."
}