pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for Tolgee

Pod holds 8 of 8 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Tolgee.

Most discussed

Make the developer experience better (lower time-to test, better test time)

🚨🚨 This bounty requires a developer who has deep knowledge and skills in Spring Boot. If you don't have such experience, contributing to this issue will probably be a waste of your precious time. Also, don't try to generate the PR with AI.

1. Problems

  • It's time consuming to write integration test for Tolgee
    • Because of the build time might be lower
    • Because the context loads in 8 seconds
    • The time to run all integration tests is ~7mins

2. Solution

  • Upgrade Spring Bo

Read the thread · 2025-03-05 · closed · 36 comments

OAuth 2.1 authorization server for token-free client auth (MCP & browser extension)

1. Problem

Every non-webapp client that talks to a Tolgee server authenticates with a static, long-lived secret, a Project API Key (PAK) or Personal Access Token (PAT) sent as the X-API-Key header (AuthenticationFilter.kt). The user generates that key in the UI, copies it, and pastes it into the client.

The reason this matters most is community translation. With public projects, a contributor is a logged-in non-member who gets an implicit "community floor" of permissions (view, suggest

Read the thread · 2026-07-27 · open · 6 comments

Add Android/Kotlin SDK format for export

For the new Android/Kotlin Compose we need to introduce new JSON format

  • We need new json format which mirrors the Android XML, but it's json
  • Choose from ICU or Java placeholders
    • For ICU, the plurals going to be ICU, Arrays going to be json arrays

Read the thread · 2025-05-13 · closed · 4 comments

Found a possible security concern

Hello 👋

I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@coderbm1) has found a potential issue, which I would be eager to share with you.

Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the f

Read the thread · 2023-07-14 · closed · external user · 3 comments

MCP support

Is your feature request related to a problem? Please describe. Support MCP (Model Context Protocol), so AI tools can easily use Tolgee API.

Describe the solution you'd like It should be possilbe to generate MCP from swagger.

Additional context Requested by a user.

Read the thread · 2025-08-13 · closed · outside contributor · 1 comment

MCP for better development with AI agents

Problem

The MCP server we ship today works but has rough edges that limit how well AI coding agents (Claude, Cursor, etc.) can integrate Tolgee into a real development workflow. These issues accumulated as we iterated on individual features; this pitch bundles the fixes and the follow-up work into one coherent direction.

Context: #3574.

Solution

1. create_keys accepts full key metadata in one call

Auto-translation runs immediately after key creation and uses description, `comme

Read the thread · 2026-04-23 · open · 0 comments

Tolgee MCP server

Tolgee MCP Server Pitch

1. Problem

Developers and vibecoders manually integrate Tolgee into their applications today - reading docs, setting up SDKs, creating keys in the UI, and copying API keys. While AI assistants (Claude Code, Cursor, etc.) can write code for them, they have no access to the Tolgee platform itself. This creates a disconnected workflow:

  • Developers must context-switch between their development and Tolgee tools to create keys, configure projects and languages, or

Read the thread · 2026-02-04 · closed · 0 comments

Fix image timestamp validation

Considering the "secret key" is just a timestamp derived with the instance's secret key, it seems to me any key would be capable of unlocking access to any image throughout the instance which seems quite a weak access control

Wouldn't it be better to derive the timestamp and the target screenshot id, so no other items can be enumerated or accessed with a given secret? 🤔

Read the thread · 2022-08-01 · closed · 0 comments

Most recent

The remaining reports are on the project's issue tracker.