{
    "version": "ifuri.search.v1",
    "generatedAt": "2026-06-19T21:36:52+00:00",
    "site": {
        "baseUrl": "https://connect.ifuri.com",
        "title": "ifuri Connect - URI connector hub for urirun",
        "description": "Install ifuri and urirun connectors from one catalog. Each connector documents its URI schemes, routes, requirements, install command and registry contract.",
        "image": "https://connect.ifuri.com/assets/social-card.svg",
        "ecosystem": [
            {
                "label": "ifuri.com",
                "url": "https://ifuri.com",
                "title": "Main site"
            },
            {
                "label": "get.ifuri.com",
                "url": "https://get.ifuri.com",
                "title": "One-line node + connector installers"
            },
            {
                "label": "Docs",
                "url": "https://docs.ifuri.com/connectors.html",
                "title": "Connector documentation"
            }
        ]
    },
    "recordCount": 26,
    "records": [
        {
            "type": "connector",
            "id": "planfile",
            "title": "Planfile Tasks",
            "status": "available",
            "category": "Planning",
            "summary": "Plan, group and execute daily tasks through task:// and planfile:// URI commands.",
            "uriSchemes": [
                "task",
                "planfile"
            ],
            "routes": [
                "task://host/tickets/query/list",
                "task://host/ticket/command/create",
                "planfile://host/dsl/command/run"
            ],
            "url": "https://connect.ifuri.com/connectors/planfile",
            "manifestUrl": "https://connect.ifuri.com/connectors/planfile.json",
            "text": "planfile Planfile Tasks available Planning Plan, group and execute daily tasks through task:// and planfile:// URI commands. Planfile Tasks turns a local planfile project into URI-addressable work items. It is the connector for daily tasks, sprint grouping, status changes and LLM-generated task execution plans. task planfile tasks planfile todo sprint LLM workflow Create tasks from chat or a host workflow. Group tasks into sprint-like queues. Run planfile DSL from the same URI registry as other automation. task://host/tickets/query/list task://host/ticket/command/create planfile://host/dsl/command/run"
        },
        {
            "type": "route",
            "id": "planfile:task://host/tickets/query/list",
            "connectorId": "planfile",
            "connectorName": "Planfile Tasks",
            "route": "task://host/tickets/query/list",
            "scheme": "task",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/planfile#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/planfile.json",
            "text": "task://host/tickets/query/list Planfile Tasks Plan, group and execute daily tasks through task:// and planfile:// URI commands."
        },
        {
            "type": "route",
            "id": "planfile:task://host/ticket/command/create",
            "connectorId": "planfile",
            "connectorName": "Planfile Tasks",
            "route": "task://host/ticket/command/create",
            "scheme": "task",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/planfile#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/planfile.json",
            "text": "task://host/ticket/command/create Planfile Tasks Plan, group and execute daily tasks through task:// and planfile:// URI commands."
        },
        {
            "type": "route",
            "id": "planfile:planfile://host/dsl/command/run",
            "connectorId": "planfile",
            "connectorName": "Planfile Tasks",
            "route": "planfile://host/dsl/command/run",
            "scheme": "planfile",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/planfile#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/planfile.json",
            "text": "planfile://host/dsl/command/run Planfile Tasks Plan, group and execute daily tasks through task:// and planfile:// URI commands."
        },
        {
            "type": "connector",
            "id": "sqlite-context",
            "title": "SQLite Context Store",
            "status": "available",
            "category": "Data",
            "summary": "Local data, artifacts, checks and logs over data://, artifact://, check:// and log://.",
            "uriSchemes": [
                "data",
                "artifact",
                "check",
                "log"
            ],
            "routes": [
                "data://host/records/query/search",
                "artifact://host/artifacts/query/list",
                "log://host/logs/query/recent"
            ],
            "url": "https://connect.ifuri.com/connectors/sqlite-context",
            "manifestUrl": "https://connect.ifuri.com/connectors/sqlite-context.json",
            "text": "sqlite-context SQLite Context Store available Data Local data, artifacts, checks and logs over data://, artifact://, check:// and log://. SQLite Context Store gives the host a small durable memory for records, artifacts, checks and logs. It is useful for workflows that need to remember what was checked, imported, generated or changed. data artifact check log sqlite context logs artifacts memory Store structured context imported by an LLM. List artifacts created by automation. Show backend and node logs in the host UI. data://host/records/query/search artifact://host/artifacts/query/list log://host/logs/query/recent"
        },
        {
            "type": "route",
            "id": "sqlite-context:data://host/records/query/search",
            "connectorId": "sqlite-context",
            "connectorName": "SQLite Context Store",
            "route": "data://host/records/query/search",
            "scheme": "data",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/sqlite-context#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/sqlite-context.json",
            "text": "data://host/records/query/search SQLite Context Store Local data, artifacts, checks and logs over data://, artifact://, check:// and log://."
        },
        {
            "type": "route",
            "id": "sqlite-context:artifact://host/artifacts/query/list",
            "connectorId": "sqlite-context",
            "connectorName": "SQLite Context Store",
            "route": "artifact://host/artifacts/query/list",
            "scheme": "artifact",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/sqlite-context#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/sqlite-context.json",
            "text": "artifact://host/artifacts/query/list SQLite Context Store Local data, artifacts, checks and logs over data://, artifact://, check:// and log://."
        },
        {
            "type": "route",
            "id": "sqlite-context:log://host/logs/query/recent",
            "connectorId": "sqlite-context",
            "connectorName": "SQLite Context Store",
            "route": "log://host/logs/query/recent",
            "scheme": "log",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/sqlite-context#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/sqlite-context.json",
            "text": "log://host/logs/query/recent SQLite Context Store Local data, artifacts, checks and logs over data://, artifact://, check:// and log://."
        },
        {
            "type": "connector",
            "id": "domain-monitor",
            "title": "Domain Monitor",
            "status": "available",
            "category": "Operations",
            "summary": "HTTP, DNS, screenshots, checks, logs and repair tickets for website operations.",
            "uriSchemes": [
                "monitor",
                "dns",
                "flow",
                "check",
                "log"
            ],
            "routes": [
                "monitor://host/http/query/status",
                "dns://host/records/query/current",
                "flow://host/domain/command/check"
            ],
            "url": "https://connect.ifuri.com/connectors/domain-monitor",
            "manifestUrl": "https://connect.ifuri.com/connectors/domain-monitor.json",
            "text": "domain-monitor Domain Monitor available Operations HTTP, DNS, screenshots, checks, logs and repair tickets for website operations. Domain Monitor is the operational connector for recurring website checks. It can query HTTP status, inspect DNS state, create logs and prepare repair tickets when a domain fails validation. monitor dns flow check log domain monitoring DNS HTTP operations Check if a site responds correctly. Compare expected and current DNS records. Create task tickets for failed domain checks. monitor://host/http/query/status dns://host/records/query/current flow://host/domain/command/check"
        },
        {
            "type": "route",
            "id": "domain-monitor:monitor://host/http/query/status",
            "connectorId": "domain-monitor",
            "connectorName": "Domain Monitor",
            "route": "monitor://host/http/query/status",
            "scheme": "monitor",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/domain-monitor#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/domain-monitor.json",
            "text": "monitor://host/http/query/status Domain Monitor HTTP, DNS, screenshots, checks, logs and repair tickets for website operations."
        },
        {
            "type": "route",
            "id": "domain-monitor:dns://host/records/query/current",
            "connectorId": "domain-monitor",
            "connectorName": "Domain Monitor",
            "route": "dns://host/records/query/current",
            "scheme": "dns",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/domain-monitor#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/domain-monitor.json",
            "text": "dns://host/records/query/current Domain Monitor HTTP, DNS, screenshots, checks, logs and repair tickets for website operations."
        },
        {
            "type": "route",
            "id": "domain-monitor:flow://host/domain/command/check",
            "connectorId": "domain-monitor",
            "connectorName": "Domain Monitor",
            "route": "flow://host/domain/command/check",
            "scheme": "flow",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/domain-monitor#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/domain-monitor.json",
            "text": "flow://host/domain/command/check Domain Monitor HTTP, DNS, screenshots, checks, logs and repair tickets for website operations."
        },
        {
            "type": "connector",
            "id": "http-check",
            "title": "HTTP Check",
            "status": "available",
            "category": "Operations",
            "summary": "Check HTTP endpoints through httpcheck:// URI commands and a small Python CLI.",
            "uriSchemes": [
                "httpcheck"
            ],
            "routes": [
                "httpcheck://host/http/query/status"
            ],
            "url": "https://connect.ifuri.com/connectors/http-check",
            "manifestUrl": "https://connect.ifuri.com/connectors/http-check.json",
            "text": "http-check HTTP Check available Operations Check HTTP endpoints through httpcheck:// URI commands and a small Python CLI. HTTP Check is a minimal external urirun connector package. It verifies that a URL responds, optionally checks an expected status code, and returns structured JSON for host workflows, smoke tests and daily operations. httpcheck http status monitoring smoke test connector Check that a website responds with HTTP 200. Use a small external connector package in ifuri flows. Prove that connect.ifuri.com can install connector packages from GitHub. httpcheck://host/http/query/status"
        },
        {
            "type": "route",
            "id": "http-check:httpcheck://host/http/query/status",
            "connectorId": "http-check",
            "connectorName": "HTTP Check",
            "route": "httpcheck://host/http/query/status",
            "scheme": "httpcheck",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/http-check#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/http-check.json",
            "text": "httpcheck://host/http/query/status HTTP Check Check HTTP endpoints through httpcheck:// URI commands and a small Python CLI."
        },
        {
            "type": "connector",
            "id": "namecheap-dns",
            "title": "Namecheap DNS",
            "status": "available",
            "category": "DNS",
            "summary": "Safe DNS plan, backup and apply flow for Namecheap host records.",
            "uriSchemes": [
                "dns"
            ],
            "routes": [
                "dns://host/records/command/plan",
                "dns://host/records/command/backup",
                "dns://host/records/command/apply"
            ],
            "url": "https://connect.ifuri.com/connectors/namecheap-dns",
            "manifestUrl": "https://connect.ifuri.com/connectors/namecheap-dns.json",
            "text": "namecheap-dns Namecheap DNS available DNS Safe DNS plan, backup and apply flow for Namecheap host records. Namecheap DNS wraps the Namecheap API as URI commands. Workflows can plan changes, back up current host records and apply a reviewed DNS update without hard-coding SDK calls in the host app. dns Namecheap DNS records domain API Generate a DNS change plan from desired records. Back up Namecheap host records before a change. Apply reviewed DNS records from a host workflow. dns://host/records/command/plan dns://host/records/command/backup dns://host/records/command/apply"
        },
        {
            "type": "route",
            "id": "namecheap-dns:dns://host/records/command/plan",
            "connectorId": "namecheap-dns",
            "connectorName": "Namecheap DNS",
            "route": "dns://host/records/command/plan",
            "scheme": "dns",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/namecheap-dns#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/namecheap-dns.json",
            "text": "dns://host/records/command/plan Namecheap DNS Safe DNS plan, backup and apply flow for Namecheap host records."
        },
        {
            "type": "route",
            "id": "namecheap-dns:dns://host/records/command/backup",
            "connectorId": "namecheap-dns",
            "connectorName": "Namecheap DNS",
            "route": "dns://host/records/command/backup",
            "scheme": "dns",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/namecheap-dns#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/namecheap-dns.json",
            "text": "dns://host/records/command/backup Namecheap DNS Safe DNS plan, backup and apply flow for Namecheap host records."
        },
        {
            "type": "route",
            "id": "namecheap-dns:dns://host/records/command/apply",
            "connectorId": "namecheap-dns",
            "connectorName": "Namecheap DNS",
            "route": "dns://host/records/command/apply",
            "scheme": "dns",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/namecheap-dns#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/namecheap-dns.json",
            "text": "dns://host/records/command/apply Namecheap DNS Safe DNS plan, backup and apply flow for Namecheap host records."
        },
        {
            "type": "connector",
            "id": "grpc-transport",
            "title": "gRPC Transport",
            "status": "available",
            "category": "Transport",
            "summary": "Expose and call URI registries over gRPC for service-to-service communication.",
            "uriSchemes": [
                "transport"
            ],
            "routes": [
                "transport://grpc/service/command/serve"
            ],
            "url": "https://connect.ifuri.com/connectors/grpc-transport",
            "manifestUrl": "https://connect.ifuri.com/connectors/grpc-transport.json",
            "text": "grpc-transport gRPC Transport available Transport Expose and call URI registries over gRPC for service-to-service communication. gRPC Transport is a transport connector for exposing URI registries between services. It keeps the same URI binding contract while switching the network transport to gRPC. transport gRPC transport service registry runtime Expose a runtime registry to another service. Use URI routes over gRPC instead of only HTTP. Test service-to-service URI execution contracts. transport://grpc/service/command/serve"
        },
        {
            "type": "route",
            "id": "grpc-transport:transport://grpc/service/command/serve",
            "connectorId": "grpc-transport",
            "connectorName": "gRPC Transport",
            "route": "transport://grpc/service/command/serve",
            "scheme": "transport",
            "status": "available",
            "url": "https://connect.ifuri.com/connectors/grpc-transport#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/grpc-transport.json",
            "text": "transport://grpc/service/command/serve gRPC Transport Expose and call URI registries over gRPC for service-to-service communication."
        },
        {
            "type": "connector",
            "id": "mqtt",
            "title": "MQTT Device Bridge",
            "status": "planned",
            "category": "IoT",
            "summary": "Publish, subscribe and bridge firmware/backend/frontend device commands through MQTT URI routes.",
            "uriSchemes": [
                "mqtt",
                "device"
            ],
            "routes": [
                "mqtt://broker/topic/command/publish",
                "device://device-01/led/command/set"
            ],
            "url": "https://connect.ifuri.com/connectors/mqtt",
            "manifestUrl": "https://connect.ifuri.com/connectors/mqtt.json",
            "text": "mqtt MQTT Device Bridge planned IoT Publish, subscribe and bridge firmware/backend/frontend device commands through MQTT URI routes. MQTT Device Bridge will map device, firmware, backend and frontend actions to shared URI routes. The goal is to control firmware and read telemetry without a separate SDK per layer. mqtt device MQTT firmware device IoT telemetry Publish firmware commands from a backend flow. Use the same device URI from frontend and host. Bridge telemetry into the registry runtime. mqtt://broker/topic/command/publish device://device-01/led/command/set"
        },
        {
            "type": "route",
            "id": "mqtt:mqtt://broker/topic/command/publish",
            "connectorId": "mqtt",
            "connectorName": "MQTT Device Bridge",
            "route": "mqtt://broker/topic/command/publish",
            "scheme": "mqtt",
            "status": "planned",
            "url": "https://connect.ifuri.com/connectors/mqtt#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/mqtt.json",
            "text": "mqtt://broker/topic/command/publish MQTT Device Bridge Publish, subscribe and bridge firmware/backend/frontend device commands through MQTT URI routes."
        },
        {
            "type": "route",
            "id": "mqtt:device://device-01/led/command/set",
            "connectorId": "mqtt",
            "connectorName": "MQTT Device Bridge",
            "route": "device://device-01/led/command/set",
            "scheme": "device",
            "status": "planned",
            "url": "https://connect.ifuri.com/connectors/mqtt#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/mqtt.json",
            "text": "device://device-01/led/command/set MQTT Device Bridge Publish, subscribe and bridge firmware/backend/frontend device commands through MQTT URI routes."
        },
        {
            "type": "connector",
            "id": "browser-control",
            "title": "Browser Control",
            "status": "planned",
            "category": "Automation",
            "summary": "Drive browser actions and screenshots through browser:// URI commands for demos and QA.",
            "uriSchemes": [
                "browser"
            ],
            "routes": [
                "browser://desktop/page/command/open",
                "browser://desktop/page/command/screenshot"
            ],
            "url": "https://connect.ifuri.com/connectors/browser-control",
            "manifestUrl": "https://connect.ifuri.com/connectors/browser-control.json",
            "text": "browser-control Browser Control planned Automation Drive browser actions and screenshots through browser:// URI commands for demos and QA. Browser Control will expose browser actions as URI commands for visual checks, screenshots and demo automation. In the LAN lab it should target the noVNC machine, not the physical host browser. browser browser screenshot QA noVNC automation Open pages inside a controlled demo desktop. Capture screenshots as URI flow artifacts. Run repeatable browser QA from NL-to-flow. browser://desktop/page/command/open browser://desktop/page/command/screenshot"
        },
        {
            "type": "route",
            "id": "browser-control:browser://desktop/page/command/open",
            "connectorId": "browser-control",
            "connectorName": "Browser Control",
            "route": "browser://desktop/page/command/open",
            "scheme": "browser",
            "status": "planned",
            "url": "https://connect.ifuri.com/connectors/browser-control#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/browser-control.json",
            "text": "browser://desktop/page/command/open Browser Control Drive browser actions and screenshots through browser:// URI commands for demos and QA."
        },
        {
            "type": "route",
            "id": "browser-control:browser://desktop/page/command/screenshot",
            "connectorId": "browser-control",
            "connectorName": "Browser Control",
            "route": "browser://desktop/page/command/screenshot",
            "scheme": "browser",
            "status": "planned",
            "url": "https://connect.ifuri.com/connectors/browser-control#routes",
            "manifestUrl": "https://connect.ifuri.com/connectors/browser-control.json",
            "text": "browser://desktop/page/command/screenshot Browser Control Drive browser actions and screenshots through browser:// URI commands for demos and QA."
        }
    ]
}