agent crm MCP Resources

agent crm offers 139 resources. A resource is data the server exposes for a client to attach as context — a file, a page, an API response — rather than an action. Each has its own page, per client.

• documentation-index
• claims-ledger
• jobs-index
• AGENTS.md
• ARCHITECTURE.md
• CLAUDE.md
• CONTRIBUTING.md
• DECISIONS.md
• GEMINI.md
• PRODUCT.md
• README.md
• ROADMAP.md
• SECURITY.md
• TASKS.md
• docs/ACTIONS.md
• docs/ADMIN.md
• docs/ADMIN_SMOKE.md
• docs/AGENT_HARNESS_COMPATIBILITY.md
• docs/API.md
• docs/APPLICATION_INSPECTION.md
• docs/CODER_TOOLING_ROADMAP.md
• docs/COMMERCIAL_OPERATIONS.md
• docs/CONTRACT_ACTIVATION.md
• docs/DELIVERY_CHANGE_ACCEPTANCE.md
• docs/DELIVERY_ECONOMICS.md
• docs/DELIVERY_HANDOVER.md
• docs/FALSIFY.md
• docs/HANDOVER_CODEX.md
• docs/IMPLEMENTATION_EVIDENCE.md
• docs/JTBD.md
• docs/LEAD_INTELLIGENCE.md
• docs/MCP.md
• docs/MODULE_EVOLUTION.md
• docs/MODULE_FACTORY.md
• docs/MODULE_MANIFEST.md
• docs/PACKAGE_AUTHORING.md
• docs/PROJECT_STATUS.md
• docs/QUALITY_GATES.md
• docs/RENAME_SURFACE.md
• docs/RENEWAL_AMENDMENT.md
• docs/REPOSITORY_TRUTH.md
• docs/SCENARIO_EVIDENCE.md
• docs/SERVICE_OPERATIONS.md
• docs/SIGNATURE_ORDER.md
• docs/SKILL_PACKAGING.md
• docs/SOLUTION_PLAN.md
• docs/WORK_TASKS.md
• docs/architecture/AGENT_TOOL_SURFACE.md
• docs/architecture/EXTRACTION_PREPARATION.md
• docs/architecture/INTELLIGENCE_PACKAGE_TARGET.md
• docs/architecture/LEGACY_ALIGNMENT_MATRIX.md
• docs/benchmarks/AGENT_TOOL_SELECTION_PROTOCOL.md
• docs/benchmarks/CPR_PROTOCOL.md
• docs/benchmarks/CRM_JTBD_MATRIX.md
• docs/benchmarks/PILOT_PROTOCOL.md
• docs/benchmarks/TOOL_SELECTION_PILOT_2026-08-13.md
• docs/benchmarks/URR_PILOT_2026-08-10.md
• docs/editions/CLOUD_INTEGRATION_CONTRACT.md
• docs/editions/MANAGED_CLOUD_EDITION.md
• docs/editions/OPEN_SOURCE_EDITION.md
• docs/editions/PRIVATE_REPOSITORY_MIGRATION.md
• docs/editions/PUBLIC_ARTIFACT_POLICY.md
• docs/editions/REPOSITORY_BOUNDARY.md
• docs/evidence/commercial-extraction.md
• docs/evidence/lead-intelligence-extraction.md
• docs/jtbd/AGENTS.md
• docs/jtbd/MASTER.md
• docs/jtbd/NORMALIZATION_V1_1.md
• docs/jtbd/PORTFOLIO_ALIGNMENT.md
• docs/jtbd/PUBLIC_PRIVATE.md
• docs/jtbd/README.md
• docs/jtbd/coverage/MATRIX_CROSSWALK.md
• docs/jtbd/coverage/STATUS_CROSSWALK.md
• docs/jtbd/prompts/01_repo_coverage_audit.md
• docs/jtbd/prompts/02_gap_to_roadmap.md
• docs/jtbd/prompts/03_jtbd_to_spec.md
• docs/jtbd/prompts/04_competitor_benchmark.md
• docs/jtbd/prompts/05_simulate_lifecycle.md
• docs/jtbd/quality/SEMANTIC_QUALITY_FINDINGS.md
• docs/jtbd/quality_report.md
• docs/jtbd/reviews/ownership/README.md
• docs/jtbd/roadmap/OWNERSHIP.md
• docs/marketing/AWESOME_LIST_SUBMISSIONS.md
• docs/marketing/BENCHMARK_ARCHITECTURE.md
• docs/marketing/BENCHMARK_PUBLICATION.md
• docs/marketing/CONTENT_PILLARS.md
• docs/marketing/CONTENT_PRODUCTION.md
• docs/marketing/CORRECTIONS.md
• docs/marketing/DEPLOYMENT.md
• docs/marketing/DESIGN_BRIEF.md
• docs/marketing/FOUNDER_CHECKLIST.md
• docs/marketing/GITHUB_LISTING.md
• docs/marketing/LAUNCH_PACKET.md
• docs/marketing/NAME_VERIFICATION.md
• docs/marketing/OBJECTIONS.md
• docs/marketing/PENDING_HUMAN_SUBMISSION.md
• docs/marketing/RECONCILIATION_AUDIT_2026-08-24.md
• docs/marketing/ROUNDUP_OUTREACH.md
• docs/marketing/SITE_ARCHITECTURE.md
• docs/marketing/drafts/2026-08-09-indie-hackers-refusal-surface.md
• docs/strategy/AGENTIC_CRM_RESEARCH_2026_09.md
• docs/strategy/AGENTIC_WORKFORCE_ROADMAP.md
• docs/strategy/AGENT_CRM_CLOUD.md
• docs/strategy/AGENT_DISCOVERY.md
• docs/strategy/AGENT_RECOMMENDATION.md
• docs/strategy/ANALYTICS_STUDIO.md
• docs/strategy/BRAND_REQUIREMENTS.md
• docs/strategy/CAMPAIGNS_JOURNEYS.md
• docs/strategy/CATEGORY.md
• docs/strategy/CLOUD_JTBD.md
• docs/strategy/CODING_AGENT_DX_NORTH_STAR.md
• docs/strategy/COMPETITOR_MAP.md
• docs/strategy/CONTRACT_SUBSCRIPTION_RENEWAL.md
• docs/strategy/CRM_BUILD_BENCHMARK.md
• docs/strategy/CUSTOMER_REVENUE_OS_ROADMAP.md
• docs/strategy/DATA_GOVERNANCE.md
• docs/strategy/DELIVERY_SERVICE.md
• docs/strategy/DESIGN_TO_CRM.md
• docs/strategy/DISTRIBUTION_SUBMISSIONS.md
• docs/strategy/EXECUTION_ROADMAP.md
• docs/strategy/EXPERIMENTATION_ATTRIBUTION.md
• docs/strategy/EXTERNAL_REVIEW.md
• docs/strategy/FACTORY_ACCORDO_INTEGRATION_ROADMAP.md
• docs/strategy/GO_TO_MARKET.md
• docs/strategy/GTM_TECHNICAL_EVIDENCE_HANDOFF.md
• docs/strategy/GUIDED_ONBOARDING_AND_VERTICAL_BLUEPRINTS.md
• docs/strategy/INTEGRATION_RUNTIME.md
• docs/strategy/JOBS_AND_OUTBOX.md
• docs/strategy/MARKETING_GROWTH_OPERATIONS.md
• docs/strategy/MASTER_PLAN.md
• docs/strategy/MEDUSA_PLAYBOOK.md
• docs/strategy/NORTH_STAR_EXPERIENCE.md
• docs/strategy/OBJECTIVE_DRIVEN_AGENT_EXPERIENCE.md
• docs/strategy/OBJECTIVE_DRIVEN_FUNNEL_EXAMPLE.md
• docs/strategy/ORGANIC_GROWTH.md
• docs/strategy/PLATFORM_ALIGNMENT_GATE.md
• docs/strategy/PLATFORM_CAPABILITIES.md
• docs/strategy/RECOMMENDATION_MAP.md
• docs/strategy/REVENUE_OPERATIONS.md

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.