Sylphie MCP connector

Sylphie connects Claude to Rocket Learning’s documents, skills and tools.

Add Sylphie to Claude once. After that, any chat can search and read what colleagues have shared with you in Drive, follow the skills people here have written down, and make things Claude can't make on its own, like videos with voice-overs. The model you already pay for does the thinking; Sylphie stores, searches and runs things.

Works in
Claude web, desktop, mobile and Code
Sign-in
Your work Google account
Address
https://rudeus.uk/sylphie/mcp
Tools
Video, voice-overs and video editing; only what Claude can't do itself

Your AI appreasoning, on your plan

claude.ai
Claude Desktop
Claude mobile
Claude Code

rudeus.uk/sylphie/mcp

Sylphie

  • MCP over HTTPS
  • Google sign-in

KnowledgeDrive folders → Vertex AI Search

Live
  • Folders you share
  • Follows Drive sharing
  • Reads whole documents
  • Team libraries
  • + any folder you share

SkillsSKILL.md in Sylphie, with versions

Live
  • Org skills
  • Team skills
  • Personal skills
  • + from a chat or the Sylphie page

ToolsSealed containers on a private VM

Live
  • Remotion video
  • Voice-overs
  • Video editing
  • + tools/your-tool/
  • Status
  • Live
  • Building
  • Next

On your own plan

Reading, reasoning, writing code and choosing the next call. It counts against your plan's usage limits.

On our server

File storage, document search and sealed job containers. None of it runs a chat model.

02 · Tool list

What your AI app sees when you connect

Sylphie adds these tools to the app. The model decides when to call them, and every call shows up in the chat with what it sent and what came back. The read-only ones can run without asking you. Anything that writes files or starts a job can be set to wait for your OK.

tools/list · what Sylphie tells the app22 tools

Knowledge

  • search_knowledge

    Search everything shared with you. Returns excerpts with the document and its Drive link.

    Live
  • read_document

    Read a whole document in order, long ones in parts, or just the part that matters.

    Live
  • list_sections

    See what you can reach, the document titles, and who it's shared with.

    Live
  • share_section

    Add Sylphie teams or groups on top of a folder's Drive sharing.

    Live

Skills

  • list_skills

    The skills you can use, with a line on when to use each one.

    Live
  • read_skill

    Load a skill's steps and examples before starting the work.

    Live
  • save_skill

    Turn a chat that went well into a skill. It's yours until you share it.

    Live
  • report_skill

    Tell a skill's owner it got something wrong.

    Live

Tools

  • list_tools · read_tool_instructions

    What is installed, and how to use each tool.

    Live
  • create_workspace · list_workspaces

    Start a project, or pick one up from last week.

    Live
  • list_files · read_file · write_files

    Work on the project's files.

    Live
  • run_command

    Run a command in a sealed container.

    Live
  • start_render

    Render a preview frame or the finished video.

    Live
  • speak

    A voice-over line, saved into the project with its exact length.

    Live
  • get_job · cancel_job

    Check on a job, or stop it.

    Live
  • inspect_image

    Hands the model the rendered PNG itself, so it can look at it.

    Live
  • get_artifact

    A download link for the result, good for 30 minutes.

    Live

03 · Examples

One request at a time, traced

Four things someone might ask for, and the calls the model makes to get there. The first two work today. The other two lean on parts that are still being built, and the steps that need them are marked.

Chat

You

What does our curriculum guide say about screen time for children under three? Quote it, with page numbers.

Reply

Page 12: “No screen time before age two, apart from video calls with family, and no more than an hour a day up to age five.” Page 31 says the same for home visits. The Parent FAQ still says an hour a day at any age, so it's out of date on this.

Calls · 2Works today

  1. search_knowledge

    {"query": "screen time under three"}

    5 excerpts: Curriculum Guide.pdf p. 12 and p. 31, and Parent FAQ.docx

  2. read_document

    {"document": "Curriculum Guide.pdf", "section": "screen time"}

    The full passage from pages 12 and 13

    Curriculum Guide.pdf · p. 12

    … No screen time before age two, apart from video calls with family, and no more than an hour a day up to age five. Where a phone is the only way a family receives activities, the adult watches first and then does the activity with the child away from the screen. …

Chat

You

Make a 20-second video for parents explaining the water play activity. Follow our parent message style.

Reply

Here's the video. In the first preview the caption ran off the screen, so I made it smaller and wrapped it before the final render.

Calls · 10Works today

  1. search_knowledge

    {"query": "water play activity"}

    Activity Cards Term 2.pdf, p. 4

  2. read_skill

    {"name": "parent-message-style"}

    Short sentences. One thing to do today. Name the materials.

  3. read_tool_instructions

    {"tool": "remotion"}

    How to edit, preview and render

  4. create_workspace

    {"title": "Water play", "tool": "remotion"}

    ws_7f3a, with the starter project in it

  5. write_files

    {"workspace_id": "ws_7f3a", "files": [{"path": "src/WaterPlay.tsx", …}, {"path": "src/Root.tsx", …}]}

    2 files written

  6. start_render

    {"workspace_id": "ws_7f3a", "kind": "still", "frame": 90}

    Queued, then succeeded: out/still-90.png

  7. inspect_image

    {"workspace_id": "ws_7f3a", "path": "out/still-90.png"}

    The caption runs off the right edge.

    Fill a bowl with water. Ask your child which spoon holds more.

  8. write_files

    {"workspace_id": "ws_7f3a", "files": [{"path": "src/WaterPlay.tsx", …}]}

    Smaller caption, wrapped onto two lines

  9. start_render

    {"workspace_id": "ws_7f3a", "kind": "video"}

    Succeeded: out/water-play.mp4, 20 seconds

  10. get_artifact

    {"workspace_id": "ws_7f3a", "path": "out/water-play.mp4"}

    Download link, good for 30 minutes

Chat

You

That worked well. Save it as a skill so the rest of the comms team can make these too.

Then

The owner fixes it, from a chat or on the Sylphie page, and the next chat that reads the skill gets the new version.

Calls · 4Works today

  1. save_skill

    {"name": "Parent explainer video", "description": "A 20-second video for parents from an activity card", "body": "…"}

    Saved as your own skill. Only you can use it so far.

    --- name: parent-explainer-video description: A 20-second video for parents from an activity card metadata: owner: you --- 1. Find the activity card with search_knowledge. 2. Write the words with parent-message-style. 3. Render stills at frames 30, 90 and 150 and look at each. 4. Render the video only once the stills are right.

  2. Looks right. Share it with the Comms team.

  3. save_skill

    {"skill_id": "priya--parent-explainer-video", "share": ["comms"], "…": "…"}

    Shared with the Comms team, with you as the owner

  4. A week later, in someone else's chat

  5. list_skills

    {}

    … parent-explainer-video: a 20-second video for parents from an activity card

  6. report_skill

    {"skill": "Parent explainer video", "problem": "Captions are too small on phones"}

    Sent to the owner, who sees it on their Skills page

File names, folder contents and replies are made up for these examples. The call names and arguments are the real ones, or the planned ones for parts still being built.

04 · Extending it

Adding a folder, a skill or a tool

Each part has one way in, and nobody has to reconnect when something is added. New files turn up in search within minutes, a new skill is there the next time the model calls list_skills, and a new tool appears in list_tools after the next deploy.

Knowledge

Share a Drive folder

Share the folder with sylphie-library@agent-tools-260930-7d8f.iam.gserviceaccount.com as an Editor, so Sylphie can see who else it's shared with. It never changes your files. Prefer Viewer? Then allow Drive sharing access once on your Sylphie page.

Claude searches for the right passages, then reads whole documents when it needs the full context, several at once if it has to. Sylphie follows Drive's own sharing. Whoever can open the folder in Drive can find it through Sylphie: specific people, a team's Google Group, everyone at a domain, or anyone with the link. Every two minutes a sync picks up new and changed files and sharing. Google Docs come in as Word files, Slides as PowerPoint and Sheets as PDF, and a file you remove leaves on the next sync. PDF, Word, PowerPoint, text and HTML files are indexed, up to 500 files per share and 20 MB per file.

For a team's core library, use a shared drive, so nothing leaves with a person. A lead claims it for the team on the Sylphie page.

Google DriveExample
  • Curriculumshared
  • Program reportsshared
  • Trainingshared
  • My draftsprivate

Library

Copied into Cloud Storage and indexed by Vertex AI Search

  • PDF
  • DOCX
  • PPTX
  • TXT
  • HTML
search_knowledge
read_document
list_sections

syncs every 2 min

Skills

Write a SKILL.md

A skill is one markdown file. It has a name and a line saying when to use it, then the steps, with a couple of examples of good output and of output that was rejected and why. That's the same format Claude uses for its own skills, so one written here can also be uploaded straight to Claude.

The model calls list_skills when a task starts and read_skill when one fits. Add a skill in one of two ways: finish a chat that went well with “save this as a skill”, or choose New skill on the Sylphie page and write it or load a SKILL.md file. A new skill is yours until you share it. Leads save team skills, which can replace an org skill for their team, and admins save org skills. Every skill names an owner, keeps its versions, and report_skill sends the owner a note when it gets something wrong.

Keep skills to how we work: house style, the steps a team agreed, what good looks like. General know-how Claude already has doesn't need a skill.

skills/parent-message-style/SKILL.mdExample
---
name: parent-message-style
description: Use for anything a parent will read or hear.
metadata:
  owner: comms team
  updated: 2026-09-30
---
Write short sentences a Class 5 reader can follow.
Give one thing to do today, not three.
Name real materials: “a steel bowl”, not “a container”.

## Good
Fill a bowl with water. Ask your child which spoon holds more.

## Rejected
Engage your child in sensory water-based exploration.
Too abstract. A parent can't picture what to do.
Lifecycle
  1. draft
  2. shared
  3. reported
  4. updated

Tools

Drop a folder into tools/

A tool is a folder with a tool.json that says what it is and what's installed, an instructions.md that tells the model how to use it, and optionally a starter project. The software goes into the sandbox image. The catalogue reads the folders, so a new tool shows up in list_tools once the image is rebuilt and deployed.

Every tool gets the same calls for files, commands, image inspection and downloads. The model can look at a rendered frame or a chart itself, see what's wrong and run it again without waiting for you. Video is the only tool with a call of its own, start_render. Remotion is installed now; the rest of the rack is what's lined up after it.

tools/
remotion/
  tool.json
  instructions.md
  template/
python/
typst/
satori/
your-tool/
tools/remotion/tool.json
{
  "id": "remotion",
  "description": "Create editable React videos, inspect PNG previews and export MP4 files.",
  "installed": [
    "Node.js",
    "React 19",
    "Remotion 4.0.530",
    "Chrome Headless Shell"
  ],
  "network_access": false
}
  • Remotion

    Video from React code: explainers, animated charts, one video for each row of a sheet.

    Node · React 19 · Remotion 4.0.530 · headless Chrome · Noto fonts for Indian scriptsLive
  • Voice-overs

    Natural narration in English with Indian accents, saved into the project and timed for captions.

    speak · Gemini TTSLive
  • Media

    Edit videos and audio you already have: captions in Indian scripts, portrait and square versions, cuts, even volume, smaller files.

    ffmpeg · libass · HarfBuzzLive
  • tools/your-tool/tool.json · instructions.md · template/

05 · Sandbox

Where jobs run

Commands and renders never run on Sylphie itself. They go over a private network to one machine with no public address. Each job gets a fresh container that sees only its own project folder, has no network, and is removed when the job ends.

from Sylphie · private network · proxy key

workspace-runner · private VM · no public IP

Container · your job

  • --network none
  • --read-only
  • --cap-drop ALL
  • 2 CPUs
  • 2 GiB
  • 256 processes

Your project folder

  • src/
  • public/
  • out/still-90.png

Container · someone else's job

  • --network none
  • --read-only
  • --cap-drop ALL
  • 2 CPUs
  • 2 GiB
  • 256 processes

Their project folder

  • data/
  • chart.py
  • chart.png

Waiting · up to 20

Running at once
2 jobs
Waiting in line
Up to 20
Commands
60 s, or up to 180 s
Renders
2 min a still, 4 a video
Project size
64 MiB
Each upload
2 MiB
Outputs per job
32 MiB
Download links
Expire after 30 min
Your files
Kept until deleted
After a restart
Cut-off jobs fail

06 · Access

Who sees what

You sign in once, with your work Google account. Sylphie keeps a keyed hash of your email as your ID. The app never passes an ID itself; Sylphie reads it from your sign-in token on every call, so no chat can ask for somebody else's files.

  1. ConnectThe app opens Sylphie's sign-in page.
  2. Google sign-inYou pick your work account. Nothing else is asked for.
  3. TokenSylphie gives the app an access token that expires and gets refreshed.
  4. Every callSylphie turns the token back into your ID before it does anything.
  • Folders you shareWhoever they're shared with in Drive
  • Team librariesThe team, and anyone else it's shared with
  • SkillsOrg, your teams' and your own
  • Your workspacesOnly you

rudeus.uk/sylphie/me shows everything you can reach through Sylphie, and why.

07 · Connecting

Adding it to your app

Every app uses the same address, and you sign in with Google.

Addresshttps://rudeus.uk/sylphie/mcpLive

claude.ai and Claude Desktop

  1. Open Settings, then Connectors.
  2. Choose Add custom connector, name it Sylphie and paste the address.
  3. Click Connect and sign in with your work Google account.

Custom connectors need a Pro, Max, Team or Enterprise plan. Once it's added, it works in the Claude mobile app too.

On Team and Enterprise an owner can add it for the whole organisation, and everyone else only has to click Connect.

Claude Code

$ claude mcp add --transport http sylphie https://rudeus.uk/sylphie/mcp

Then run /mcp inside Claude Code, pick sylphie and sign in.

Other apps

Anything that supports remote MCP servers with OAuth works too, including Cursor and VS Code.

08 · Status

Where it stands

Live means you can use it today. Building means it's being written now, and next is what comes after that.

Live

  • One address, rudeus.uk/sylphie/mcp, with Google sign-in
  • Knowledge that follows Drive sharing, including Google Groups, synced every two minutes; search plus reading whole documents
  • Skills: org, team and personal, with versions and reports
  • Video with voice-overs in sealed containers
  • The Sylphie page: what you can reach, your sections and skills, teams and activity

Building

  • New tools and skills for what Claude can't do on its own

Next

  • Use counts for each folder, skill and tool, so owners can see what gets used
  • Programme numbers, with each state team seeing its own detail