Cool Property Search Server
Reserve a streamable-http MCP slot for a future Find Me Casa property-search API so agents can query listings once the remote server is live.
Overview
casa.find-me.sub1/send-email-mcp is a MCP server for the Build phase that is intended to integrate Find Me Casa property search over streamable-http once the remote is functional.
What is this MCP server?
- Remote streamable-http endpoint at sub1.find-me.casa (documented in server schema)
- Bearer-style x-api-key header required for authenticated property search calls
- Catalog title positions it as a property search server despite the send-email slug
- Publisher lists version 0.0.9 with website alpic.ai
- Explicit catalog note: non functional server (yet)—treat as preview integration
- Server metadata version 0.0.9
- Remote URL https://sub1.find-me.casa with required secret x-api-key header
- Catalog description states non functional server (yet)
What problem does it solve?
You want agent-driven property search against Find Me Casa, but the catalogued MCP remote is still marked non functional.
Who is it for?
Builders experimenting with Find Me Casa / Alpic integrations who want MCP wiring ready before the server ships.
Skip if: Anyone who needs working property search, email automation, or production agent flows today.
What do I get? / Deliverables
When the remote goes live, registering this MCP with your x-api-key should let agents query the property API from your editor without custom scripts.
- Prepared MCP remote configuration for future property search tool calls
- Documented auth header pattern for Find Me Casa endpoints
- No dependable agent queries until the remote is marked functional
Recommended MCP Servers
Journey fit
Property-search integrations belong on the build phase because you wire external APIs into the product before launch, even when the remote endpoint is still a stub. The integrations subphase fits a hosted remote MCP that will call a third-party property API with an x-api-key header.
How it compares
Hosted API remote stub, not a self-hosted skill or a complete email MCP.
Common Questions / FAQ
Who is casa.find-me.sub1/send-email-mcp for?
Indie developers planning a property-search or Casa-related integration who use MCP clients and already have or expect a Find Me Casa API key.
When should I use casa.find-me.sub1/send-email-mcp?
Only after the publisher confirms the remote is functional; until then use it as a catalog reference for endpoint and auth shape.
How do I add casa.find-me.sub1/send-email-mcp to my agent?
Add the streamable-http remote URL https://sub1.find-me.casa in your MCP client, supply the x-api-key secret (Bearer-style per schema), and verify tools respond before relying on them in workflows.