← flocore.tech

INDIVIDUAL MCP TOOL

flocore_create_ticket

Raise an operational ticket.

flocore.technone authenticationAvailability not checked

LIVE ENDPOINT

https://fo.flocore.tech/mcp

No auth detected

Connect to this endpoint to inspect the live schema for flocore_create_ticket and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

flocore.tech

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.flocore]
url = "https://fo.flocore.tech/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "flocore": {
      "type": "http",
      "url": "https://fo.flocore.tech/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: flocore
Remote MCP URL: https://fo.flocore.tech/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "flocore": {
      "url": "https://fo.flocore.tech/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "flocore": {
      "type": "http",
      "url": "https://fo.flocore.tech/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "flocore",
  "transport": "streamable-http",
  "url": "https://fo.flocore.tech/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • aegis_inspect — Screen a prompt or text for injection, jailbreak and exfil intent.
  • flocore_list_tenants — List the tenants (customer/app operating boundaries) visible to your scoped token.
  • flocore_ontology_entities — Read the FLOCORE ontology: entity types, their semantic meaning, allowed relationships and lifecycle states.
  • flocore_list_tickets — List operational tickets for a tenant, optionally filtered by status.
  • flocore_orch_board — Read the FLOCORE orchestration board (W113 active mesh): lanes + liveness, work-queue summary, and governance caps + runaway flags.
  • flocore_queue_summary — Read the FLOCORE work-queue summary: open items by status, depth, oldest-queued age, awaiting-human, dead-letter, stuck.
  • flocore_mesh_lanes — List the FLOCORE mesh lanes with kind, capabilities and liveness (live | stale | offline).
  • flocore_recall — Ask FLOCORE's MEMORY: 'what do I know about X?