
PERSONAIZER
io.github.PersonAIzerPublished by GitHub account PersonAIzerv1.0.1Updated Oct 23, 2026
Free MCP API to create AI chat personas for websites — upload knowledge, search, and chat
Overview
A remote MCP endpoint for PersonAIzer that lets an assistant create AI chat personas for websites and query their uploaded knowledge.
- What you can do
- Create AI chat personas for websites and check their creation status using an account key. Upload knowledge documents to a persona and search that knowledge. Chat with a persona through the connected assistant. Access is split between persona secret keys for knowledge and chat operations and account keys for persona management.
- When to use it
- Useful when you want an assistant to build or manage website chat personas and to query or chat against the knowledge you have uploaded to them, without running any local software.
- Requirements
- A remote connection to the PersonAIzer endpoint over streamable HTTP. A PersonAIzer API key sent in the X-Api-Key header: a persona secret key for search, chat and knowledge upload, or an account key for creating personas and checking status. The key is obtained from the PersonAIzer developer site.
Installation
In SourceWeft
- Open PERSONAIZER in the dashboard and add it to a workspace.
- Connect X-Api-Key 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.PersonAIzer%2Fmcp/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": {
"personaizer": {
"type": "http",
"url": "https://sessions.personaizer.com/mcp",
"headers": {
"X-Api-Key": "<YOUR_API_KEY>"
}
}
}
}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 listedRequired15 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.