Skip to main content
Glama
BACH-AI-Tools

Fotocasa1 MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Fotocasa1 MCP Server

English | 简体中文 | 繁體中文

用于访问 Fotocasa1 API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-fotocasa1）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: creci-sp-api

简介

这是一个 MCP 服务器，用于访问 Fotocasa1 API。

  • PyPI 包名: bach-fotocasa1

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-fotocasa1

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-fotocasa1 bach_fotocasa1

# 或指定版本
uvx --from bach-fotocasa1@latest bach_fotocasa1

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-fotocasa1

# 运行（命令名使用下划线）
bach_fotocasa1

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-fotocasa1": {
      "command": "uvx",
      "args": ["--from", "bach-fotocasa1", "bach_fotocasa1"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-fotocasa1": {
      "command": "uvx",
      "args": ["--from", "bach-fotocasa1", "bach_fotocasa1"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

property_details

Get property details. Requires the property ID.

端点: GET /propertydetails

参数:

  • id (string) 必需: Property Id. 'Id' tag from properties listing. It should have this format: '1_123456789'. NOT to be confused with the 'propertyId', which doesn't include the first number. The first number indicates the operation. 1 is for sale, 3 is for rent.

list_properties

List Properties. Requires locationId, lat and lon which can be obtained through autocomplete endpoint. Pick the property type value to extract Homes, Premises, Garages, Offices, Box Rooms, Lands or Buildings.

端点: GET /listproperties

参数:

  • locationId (string) 必需: Also known as combinedLocationIds. Get this value from suggested locations (autocomplete endpoint). All Spain ID: 724,0,0,0,0,0,0,0,0

  • propertyType (string) 必需: Property Type to search. Default value is Homes.

  • operation (string) 必需: Example value:

  • pageNumber (number) 必需: Example value: 1

  • latitude (string) 必需: Example value: 40.4096

  • longitude (string) 必需: Example value: -3.68624

  • sorting (string) 必需: Pick between: Fotocasa Rating: scoring (default) Latest: publicationDate Cheapest: price Most expensive:

  • onlyCount (string): Example value:

  • isNewConstruction (string): Example value:

  • minPrice (number): Example value:

  • maxPrice (number): Example value:

  • minRooms (number): Minimum number of rooms. Pick between: 1, 2, 3 or 4. Anything above will be ignored.

  • minBathrooms (number): Minimum number of bathrooms. Pick between: 1, 2 and 3. Anything above will be ignored.

  • allFlats (string): Example value:

  • intermediateFloors (string): Example value:

  • apartment (string): Example value:

  • penthouse (string): Example value:

  • duplexApartment (string): Example value:

  • loftType (string): Example value:

  • groundFloor (string): Example value:

  • studioType (string): Example value:

  • allHouses (string): Example value:

  • houseOrChalet (string): Example value:

  • ruralProperty (string): Example value:

  • semiDetached (string): Example value:

get_suggestions

Get location suggestions (autocomplete)

端点: GET /getsuggestions

参数:

  • query (string) 必需: Example value: madrid

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

3 tools
get_suggestionsB

Get location suggestions (autocomplete)

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesExample value: madrid

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description does not disclose behavioral traits beyond the basic function. It fails to mention whether the operation is read-only, requires authentication, has rate limits, or any side effects. The minimal phrasing offers no additional insight into how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that communicates the essential purpose without any extraneous words. Every word earns its place, making it highly efficient and easy to process.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (one parameter, no output schema), the description is minimally adequate. However, it omits information about the output structure (e.g., whether results are strings or objects), which would be helpful for the agent to understand the return format. Slight improvement needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the input schema has 100% description coverage, the parameter description only provides an example value ('madrid'). The tool description adds context that the query is for location suggestions, which gives semantic meaning beyond the schema, but it does not elaborate on the expected format or constraints, resulting in adequate but not exceptional value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb 'get' and resource 'location suggestions', explicitly indicating autocomplete functionality. It is distinct from sibling tools list_properties and property_details, which focus on properties rather than location suggestions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention scenarios, prerequisites, or conditions under which this tool should be preferred, leaving the agent without explicit context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_propertiesA

List Properties. Requires locationId, lat and lon which can be obtained through autocomplete endpoint. Pick the property type value to extract Homes, Premises, Garages, Offices, Box Rooms, Lands or Buildings.

ParametersJSON Schema
NameRequiredDescriptionDefault
locationIdYesAlso known as combinedLocationIds. Get this value from suggested locations (autocomplete endpoint). All Spain ID: 724,0,0,0,0,0,0,0,0
propertyTypeYesProperty Type to search. Default value is Homes.
operationYesExample value:
pageNumberYesExample value: 11
latitudeYesExample value: 40.4096
longitudeYesExample value: -3.68624
sortingYesPick between: Fotocasa Rating: scoring (default) Latest: publicationDate Cheapest: price Most expensive:
onlyCountNoExample value:
isNewConstructionNoExample value:
minPriceNoExample value: 0
maxPriceNoExample value: 0
minRoomsNoMinimum number of rooms. Pick between: 1, 2, 3 or 4. Anything above will be ignored.0
minBathroomsNoMinimum number of bathrooms. Pick between: 1, 2 and 3. Anything above will be ignored.0
allFlatsNoExample value:
intermediateFloorsNoExample value:
apartmentNoExample value:
penthouseNoExample value:
duplexApartmentNoExample value:
loftTypeNoExample value:
groundFloorNoExample value:
studioTypeNoExample value:
allHousesNoExample value:
houseOrChaletNoExample value:
ruralPropertyNoExample value:
semiDetachedNoExample value:

TDQS

A3.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It does not mention that the tool is read-only, what the response contains (e.g., list of properties, count, pagination), or any side effects. It also fails to indicate that the tool requires multiple mandatory parameters or how errors are handled, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loading the purpose in the first sentence and adding prerequisite and parameter guidance in the second. Every word is functional; no wasted space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 25 parameters (7 required) and no output schema, this description is too sparse. It omits crucial context: how to combine parameters for filtering, that operation is required, and what the output looks like. The agent would need to infer or guess many usage details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining that locationId, lat, lon come from the autocomplete endpoint and that propertyType can be set to specific values like Homes, Premises, etc. However, it does not elaborate on many other parameters (e.g., minPrice, operation), relying on weak schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List Properties' as the action, identifies required parameters (locationId, lat, lon) and their source, and explains the propertyType parameter's role in filtering by property type. This differentiates it from sibling tools like get_suggestions (location autocomplete) and property_details (single property info).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description instructs the agent to obtain locationId, lat, and lon from the autocomplete endpoint, providing a clear prerequisite. It also advises picking the propertyType for extraction. However, it lacks explicit guidance on when to use this tool vs. alternatives (e.g., when to call property_details instead) or situations to avoid.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

property_detailsB

Get property details. Requires the property ID.

ParametersJSON Schema
NameRequiredDescriptionDefault
idYesProperty Id. 'Id' tag from properties listing. It should have this format: '1_123456789'. NOT to be confused with the 'propertyId', which doesn't include the first number. The first number indicates the operation. 1 is for sale, 3 is for rent.

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and the description gives no behavioral traits such as read-only nature, side effects, or error conditions. It's insufficient for an agent to understand implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise with two sentences that convey the core purpose and requirement. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description is adequate but lacks details on return value or constraints. It covers the minimum.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameter description in the schema already explains the format. The tool description adds minimal value by restating the requirement for the property ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Get' and resource 'property details' clearly indicate the tool retrieves details for a property. While it distinguishes from siblings like list_properties, it doesn't explicitly differentiate usage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. It only states the required parameter, not the context or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

Each tool has a distinct purpose: location autocomplete, property listing, and property details. No overlap in functionality.

Naming Consistency4/5

Names use consistent lowercase_with_underscores pattern. Two follow verb_noun (get_suggestions, list_properties) and one is noun_noun (property_details), which slightly deviates but remains clear.

Tool Count3/5

3 tools is minimal but reasonable for a read-only property browsing server. Could be expanded with search or filtering but not critically thin.

Completeness3/5

Covers the basic workflow of location search, property listing, and details. However, missing operations like filtering by criteria other than location or user interaction features reduces completeness.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Daft.ie MCP Server

    amineremache
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that enables interaction with the Daft.ie API for searching rental properties and retrieving detailed information about specific rental listings.
    10
    ISC

  • creci-sp-api

    opastorello
    F
    license
    Not graded
    quality
    C
    maintenance
    MCP server for querying real estate agents registered with CRECI-SP. Enables searching by name, CRECI number, city, or status, retrieving agent details, and getting statistics.
    -

  • finn-mcp

    aHk-coder
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that provides access to finn.no, Norway's largest online classifieds marketplace, enabling searches and listing retrieval across used goods, real estate, cars, and jobs.
    2
    6
    1
    MIT
  • stream-estate by StreamEstate

    stream-estateofficial

    StreamEstate
    A
    license
    A
    quality
    D
    maintenance
    MCP server for the Stream.estate French real estate API. Search properties, get market statistics, manage saved searches with webhook notifications.
    13
    52
    2
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/bachai-fotocasa1'

If you have feedback or need assistance with the MCP directory API, please join our Discord server