
ScriptSeen
io.github.yesmarsPublished by GitHub account yesmarsv1.0.0Updated Oct 24, 2026
Create short-form scripts and paced audio, then hand clips to ScriptSeen's on-device video maker.
Overview
Lets an assistant write short-form scripts and paced audio, then pass the resulting clips to ScriptSeen's on-device video maker.
- What you can do
- ScriptSeen is a remote MCP server for short-form video production. According to its description, it creates short-form scripts and paced audio, then hands the resulting clips to ScriptSeen's on-device video maker. No individual tools are listed in the manifest, so the exact operations are not documented here.
- When to use it
- Relevant when you want an assistant to draft short-form video scripts and generate paced audio as part of a clip-making workflow. It fits creators or teams already using ScriptSeen who want that pipeline reachable from an AI assistant. It is not aimed at general scripting or coding tasks.
- Requirements
- A remote MCP endpoint at over streamable HTTP. OAuth authentication is required, using an Authorization header with a Bearer personal ss_agent_ token obtained from the ScriptSeen account's AI agent access section. No packages or environment variables are declared.
Installation
In SourceWeft
- Open ScriptSeen in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.yesmars%2Fscriptseen/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"scriptseen": {
"type": "http",
"url": "https://api.scriptseen.com/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 22, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.