CRIC物业AI MCP Server

Created By
wuye-aia year ago
CRIC物业AI MCP Server
Overview

What is CRIC物业AI MCP Server?

CRIC物业AI MCP Server is an intelligent AI assistant designed specifically for the property management industry, developed by CRIC. It integrates various core capabilities to assist in industry research, legal regulations, community governance, project management, and content writing.

How to use CRIC物业AI MCP Server?

To use the MCP Server, you need to obtain a CRIC物业AI Access Token. You can run the server in either HTTP mode or Stdio mode, and connect using tools like MCP Inspector or third-party applications.

Key features of CRIC物业AI MCP Server?

  • Access to daily property industry news reports.
  • Retrieval of hot industry issues and their classifications.
  • Searchable knowledge base for property management queries.
  • High accuracy in data processing and real-time updates.

Use cases of CRIC物业AI MCP Server?

  1. Providing timely updates on property industry news.
  2. Assisting property managers with legal and regulatory information.
  3. Supporting community governance through data insights.

FAQ from CRIC物业AI MCP Server?

  • How do I obtain an Access Token?

You can contact customer service at xuanao@cric.com to request an Access Token.

  • Can I run the MCP Server locally?

Yes, you can run the MCP Server locally using the provided command in HTTP mode.

  • What is the accuracy of the data provided?

The system is designed to achieve over 90% accuracy in data processing and insights.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wuye-ai
Star
1
Language
-
License
-

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

a day ago
Wiza

9 hours ago