Street.co.uk MCP by usefulapi

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Dokumente, Tabellen & Büroarbeit

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

https://street-co-uk.usefulapi.io/mcp

claude mcp add --transport http street-co-uk https://street-co-uk.usefulapi.io/mcp

{
  "mcpServers": {
    "street-co-uk": {
      "url": "https://street-co-uk.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "street-co-uk": {
      "type": "http",
      "url": "https://street-co-uk.usefulapi.io/mcp"
    }
  }
}

https://street-co-uk.usefulapi.io/mcp

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• street_list_properties

  List properties (sales and lettings listings, with address, status, price, bedrooms and the owner link). Newest first as Street orders them; page with page and page_size. GET /properties.

• street_get_property

  One property by UUID, with the related records you ask for in include. GET /properties/{id}.

• street_list_people

  List people (contacts: name, emails, phones, addresses, contact preferences). Newest first as Street orders them; page with page and page_size. GET /people.

• street_get_person

  One person by UUID, with the related records you ask for in include. GET /people/{id}.

• street_list_vendors

  List vendors (people selling a property). Newest first as Street orders them; page with page and page_size. GET /vendors.

• street_get_vendor

  One vendor by UUID, with the related records you ask for in include. GET /vendors/{id}.

• street_list_landlords

  List landlords (people letting a property). Newest first as Street orders them; page with page and page_size. GET /landlords.

• street_get_landlord

  One landlord by UUID, with the related records you ask for in include. GET /landlords/{id}.

• street_list_tenants

  List tenants. Newest first as Street orders them; page with page and page_size. GET /tenants.

• street_get_tenant

  One tenant by UUID, with the related records you ask for in include. GET /tenants/{id}.

• street_list_sales_applicants

  List sales applicants (buyers: budget, bedrooms, areas, buying and financial position, lead rating). Newest first as Street orders them; page with page and page_size. GET /sales-applicants.

• street_get_sales_applicant

  One sales applicant by UUID, with the related records you ask for in include. GET /sales-applicants/{id}.

• street_list_lettings_applicants

  List lettings applicants (prospective tenants: budget, bedrooms, areas, furnished, lead rating). Newest first as Street orders them; page with page and page_size. GET /lettings-applicants.

• street_get_lettings_applicant

  One lettings applicant by UUID, with the related records you ask for in include. GET /lettings-applicants/{id}.

• street_list_enquiries

  List enquiries (inbound leads: who, which property, message, source). Newest first as Street orders them; page with page and page_size. GET /enquiries.

• street_get_enquiry

  One enquiry by UUID, with the related records you ask for in include. GET /enquiries/{id}.

• street_list_viewings

  List viewings (property, applicant, time, status, feedback). Newest first as Street orders them; page with page and page_size. GET /viewings.

• street_get_viewing

  One viewing by UUID, with the related records you ask for in include. GET /viewings/{id}.

• street_list_valuations

  List valuations (market appraisals: property, valuer, time, status, outcome). Newest first as Street orders them; page with page and page_size. GET /valuations.

• street_get_valuation

  One valuation by UUID, with the related records you ask for in include. GET /valuations/{id}.

• street_list_sales

  List sales (the sales progression records: agreed price, buyer, vendor, solicitors, status). Newest first as Street orders them; page with page and page_size. GET /sales.

• street_get_sale

  One sale by UUID, with the related records you ask for in include. GET /sales/{id}.

• street_list_sales_offers

  List sales offers (amount, applicant, property, status). Newest first as Street orders them; page with page and page_size. GET /sales-offers.

• street_get_sales_offer

  One sales offer by UUID, with the related records you ask for in include. GET /sales-offers/{id}.

• street_list_lettings_offers

  List lettings offers (rent, applicant, property, status). Newest first as Street orders them; page with page and page_size. GET /lettings-offers.

• street_get_lettings_offer

  One lettings offer by UUID, with the related records you ask for in include. GET /lettings-offers/{id}.

• street_list_tenancies

  List tenancies (property, tenants, owner, rent, dates). Newest first as Street orders them; page with page and page_size. GET /tenancies.

• street_get_tenancy

  One tenancy by UUID, with the related records you ask for in include. GET /tenancies/{id}.

• street_list_maintenance_jobs

  List maintenance jobs (read-only: property, status, assignee, dates). Newest first as Street orders them; page with page and page_size. GET /maintenance-jobs.

• street_get_maintenance_job

  One maintenance job by UUID, with the related records you ask for in include. GET /maintenance-jobs/{id}.

• street_list_tasks

  List tasks (to-dos with title, due date, assignee and the record they relate to). Newest first as Street orders them; page with page and page_size. GET /todos.

• street_list_follow_ups

  List follow-ups (due date, note, and the property, applicant, sale or valuation they belong to). Newest first as Street orders them; page with page and page_size. GET /follow-ups.

• street_list_branches

  List branches (name, address, contact details). Newest first as Street orders them; page with page and page_size. GET /branches.

• street_get_branch

  One branch by UUID, with the related records you ask for in include. GET /branches/{id}.

• street_list_users

  List users (the agency's staff: name, job title, contact details, deactivated state). Newest first as Street orders them; page with page and page_size. GET /users.

• street_get_user

  One user by UUID, with the related records you ask for in include. GET /users/{id}.

• street_list_invoices

  List invoices (client accounting: property, owner, line items, paid and voided state). Newest first as Street orders them; page with page and page_size. GET /invoices.

• street_get_invoice

  One invoice by UUID, with the related records you ask for in include. GET /invoices/{id}.

• street_list_sales_instructions

  List sales instructions (an agreement to sell: property, owner, fees). Newest first as Street orders them; page with page and page_size. GET /sales-instructions.

• street_get_sales_instruction

  One sales instruction by UUID, with the related records you ask for in include. GET /sales-instructions/{id}.

• street_list_lettings_instructions

  List lettings instructions (an agreement to let: property, owner). Newest first as Street orders them; page with page and page_size. GET /lettings-instructions.

• street_get_lettings_instruction

  One lettings instruction by UUID, with the related records you ask for in include. GET /lettings-instructions/{id}.

• street_list_inspections

  List property inspections (due date, booked date, inspector, status). Newest first as Street orders them; page with page and page_size. GET /inspections.

• street_get_inspection

  One inspection by UUID, with the related records you ask for in include. GET /inspections/{id}.

• street_list_interested_applicants

  List interested applicants (applicants who showed interest in a property). Newest first as Street orders them; page with page and page_size. GET /interested-applicants.

• street_get_interested_applicant

  One interested applicant by UUID, with the related records you ask for in include. GET /interested-applicants/{id}.

• street_list_task_types

  List task types (the categories a task can have; use an id as task_type_id when creating a task). Newest first as Street orders them; page with page and page_size. GET /todo-types.

• street_list_areas

  List areas (the area names used to match applicants and properties). Newest first as Street orders them; page with page and page_size. GET /areas.

• street_create_enquiry

  WRITE: record a new inbound enquiry (a lead) in Street. Street matches the email address to an existing person or creates one, and the agency's own automations may then email or assign the lead. Street requires the enquiry to be tied to exactly one record: pass property_id, or sa

• street_create_note

  WRITE: add a note to one Street record (a person, property, applicant, sale, viewing, tenancy and so on). The note is visible to the agency's staff. Not idempotent: calling it twice adds two notes. POST /notes.

• street_create_task

  WRITE: create a task (to-do) in Street, optionally assigned to a user and given a task type. Not idempotent: calling it twice creates two tasks. POST /todos.

• street_create_follow_up

  WRITE: schedule a follow-up on a property, sales or lettings applicant, sale or valuation. Not idempotent: calling it twice creates two follow-ups. POST /follow-ups.

• street_create_maintenance_request

  WRITE: log a maintenance request against a property (a request, not a job: Street staff turn it into a job). Not idempotent: calling it twice logs two requests. POST /maintenance-requests.

• street_update_person

  WRITE: change a person's title, name, marketing consent or contact preferences in Street. Street requires both names on every update, so the current record is read first and anything you leave out is sent back unchanged. Contact details (email, phone, address) cannot be changed t

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026

• ✓ Bestanden

  Entwickler passt zum Repo

  Der Registry-Name wurde über die Domain usefulapi.io bestätigt (die Registry prüft, wem die Domain gehört)

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 229 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 54 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Dokumente, Tabellen & Büroarbeiti

• Mehr Sterne als 0 % der anderen 2186 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 97 % der anderen 2186 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 100 % der anderen 2186 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

{