Skip to main content

Connect Serval to Raycast

Give Raycast governed access to Serval’s 402 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Serval to Raycast in four steps

Admins approve the server once. Everyone in Raycast then gets it through the same governed connection.

  1. 1

    Add Serval to Runlayer

    Serval isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Raycast to Runlayer

    Users add the Runlayer Plugin to Raycast by following Runlayer’s setup guide. Raycast reaches Serval’s 402 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Raycast setup guide
  3. 3

    Sign in to Serval

    Sign in the way Serval requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Serval from Raycast

    Serval’s approved tools appear in Raycast. Every call is checked against policy and recorded.

Tools

402 Serval tools in Raycast

Runlayer policy decides which of these Raycast users can call.

  • Add entity type field

    Deprecated: use POST /v2/entity-type-fields.

  • Add label to app instance

    DEPRECATED: use AddTagToSubject.

  • Add tag to subject

    Attach a tag to a subject (resource, role, app instance, workflow, or guidance).

  • Add ticket assignment group

    Add a group to the team's configured assignment groups.

  • Add ticket relevant asset

    Add a relevant asset to a ticket.

  • Aggregate entities

    Aggregate live-entity counts for one entity schema (database), grouped by entity type or by creation-time bucket (day or month).

  • Archive entity

    Archive an entity, hiding it from active browse while keeping its key reserved so the key cannot be reused.

  • Archive ticket

    Move a ticket into cold storage, removing it from most views.

See all 402 Serval tools

Control

What Runlayer can see and stop in Raycast

Some controls apply to every client at the gateway. Others depend on what Raycast exposes to Runlayer.

  • Gateway policy (available)

    Every Serval call from Raycast passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Raycast as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for Raycast yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination