
YokuApp
io.github.YokuAppPublished by GitHub account YokuAppv1.0.1Updated Oct 24, 2026
Yoku is a platform that provides structured, real-time brand identity and company data.
Overview
YokuApp connects an assistant to Yoku's platform for structured, real-time brand identity and company data, over a remote endpoint or a local npm process.
- What you can do
- Query Yoku's platform for structured, real-time brand identity and company data, using the tools the server exposes once authenticated. No tool list is published, so the exact operations are not documented here. The server can be reached either as a hosted remote endpoint or as a local stdio process from the npm package.
- When to use it
- Use it when an assistant needs brand identity or company information from Yoku and you already have a Yoku API key. It is less useful if you cannot confirm which tools it exposes or do not need Yoku's data.
- Requirements
- A Yoku API key, supplied as the YOKU_API_KEY environment variable for the local package or as a Bearer token in the Authorization header for the remote endpoint. Network access to the Yoku API; optional settings cover the API base URL, CDN base URL and request timeout. The local option needs Node.js for the npm package.
Installation
In SourceWeft
- Open YokuApp in the dashboard and add it to a workspace.
- Connect Authorization token 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.YokuApp%2Fmcp-server/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.
{
"mcpServers": {
"yokuapp": {
"type": "http",
"url": "https://mcp.yoku.app/",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.1LatestSep 16, 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.