Ollang MCP in Devin
Devin is an autonomous AI software engineer by Cognition. With Ollang MCP, Devin can handle localization and translation tasks as part of its agentic coding workflows — no human intervention required.
Setup
Open your Devin organization settings
Go to app.devin.ai and navigate to Settings > Integrations > MCP Servers. Add Ollang MCP server
Click “Add MCP Server” and enter the following configuration:{
"name": "ollang",
"url": "https://mcp.ollang.com/mcp",
"transport": "sse"
}
Authenticate
Once connected, Devin will prompt for Ollang authentication during the first tool use. Complete the OAuth sign-in flow in your browser and return to Devin.
Assign Ollang tasks to Devin
In any Devin session, you can now delegate translation tasks directly. Devin will use Ollang MCP tools autonomously to complete them.
Use Cases
Automate i18n file translation during development
Devin can manage your entire localization pipeline end-to-end:
In the repo, find all JSON locale files under src/locales/en/. Upload each
file to Ollang and create document translation orders for French (fr),
German (de), Spanish (es), and Japanese (ja). Save the returned order IDs
to a file called localization-orders.json.
Go through all TypeScript files in src/lib/. Extract all JSDoc comment
blocks, upload them as a document to Ollang for translation to Arabic,
then create a new file src/lib/docs-ar.md with the translated comments.
Monitor and download completed translations
Check the status of all Ollang orders listed in localization-orders.json.
For any orders that are completed, download the translated files and place
them in the correct src/locales/{lang}/ directories.
Integrate translation into CI workflows
Devin can be used as part of automated pipelines. Example task:
When a new locale string is added to en.json, automatically create
Ollang translation orders for all supported languages, wait for
completion, and open a pull request with the translated locale files.
Multi-Server Configuration
Combine Ollang with other MCP servers in Devin’s settings for richer workflows:
{
"mcpServers": [
{
"name": "ollang",
"url": "https://mcp.ollang.com/mcp",
"transport": "sse"
},
{
"name": "github",
"url": "https://api.githubcopilot.com/mcp/",
"transport": "sse"
}
]
}
Devin works best with Ollang when given clear success criteria — for example, “create orders and confirm order IDs are returned” rather than open-ended tasks. This helps Devin verify completion autonomously.