# Wrike > Wrike is a hosted work management platform for tasks, projects, folders, approvals and request forms. Agents reach it through REST API v4 and an official remote MCP server at mcp.wrike.com/v2 with 29 documented tools. - Canonical: https://www.anchorterminal.com/tools/wrike - Markdown: https://www.anchorterminal.com/tools/wrike.md (~7,600 tokens) - Slim: https://www.anchorterminal.com/tools/wrike.min.md (~1,930 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/wrike.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade C · 60.1/100 · rank #364 of 629 · #6 in Project & task management · not agent-ready · confidence medium** ## Assessment The official MCP server has 29 documented tools for search, task and project creation, bulk updates, comments and approvals, and it works on every plan including Free. Permanent access tokens never expire and carry the user's full access, and no SLA, official SDK or deprecation policy was found in the reviewed documentation. ## Facts | Field | Value | | --- | --- | | Vendor | Wrike, Inc. (https://www.wrike.com) | | Kind | HTTP API | | Category | Project & task management (https://www.anchorterminal.com/categories/project-management) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://www.wrike.com/api/v4` | | Auth | OAuth or key · Self-serve. Any Wrike user with API permission creates an API app under Apps & Integrations and gets an OAuth client ID and secret, with no app review. The API uses the OAuth 2.0 authorisation code flow with scopes such as wsReadOnly and wsReadWrite, one-hour access tokens and refresh tokens. A permanent access token from the same app never expires and acts with all of its user's access. The MCP server at mcp.wrike.com/v2 takes OAuth 2.0 through an admin-created app or a permanent token as a Bearer header. Clients that need dynamic client registration are told to use the permanent token. Password resets and deactivation revoke tokens. | | Pricing | Freemium ($10 / seat-mo) · The API and the MCP server are included on every plan, and Wrike charges nothing per call. Free is $0, Team $10 a user a month (2 to 15 users), Business $25 a user a month (5 to 200 users), and Pinnacle and Apex are quoted by sales. A 14-day trial needs no card, so an agent's owner can start on Free or the trial without a contract. Some fields and tools depend on the plan (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the developer docs, the llms.txt index or the pricing page (checked 2026-10-08). | | Licence | Proprietary service under Wrike's terms. The agent skills repository on GitHub is MIT | | Tools exposed | 29 | | Source | https://github.com/wrike/agent-skills | | Docs | https://developers.wrike.com | | llms.txt | https://developers.wrike.com/llms.txt | | Last release | 2026-09-17 | | Surfaces | REST API v4 at https:///api/v4 (www.wrike.com, app-eu.wrike.com, app-us2.wrike.com) and the remote MCP server v2 at https://mcp.wrike.com/v2 (Streamable HTTP) | | MCP tools | 29 documented. Read: search_spaces, get_items_children, get_my_inbox, search_items, search_users, get_users, get_item_details, get_item_comments, search_blueprints, search_requestforms, get_requestform, prefill_requestform, get_async_job, recommend_resources (Wrike Labs, Pinnacle and Apex), search_workflows, search_customitemtypes, search_item_customfields, get_approvals, search_approvals. Write: create_task_item, create_project_folder_item, create_item_from_blueprint, submit_requestform, update_items, create_item_comment, prepare_attachment_upload, add_attachments_to_item, add_whiteboard_to_item, remove_whiteboard_from_item | | Credentials | OAuth 2.0 authorisation code flow with a client ID and secret from an API app, one-hour access tokens and refresh tokens. Permanent access tokens never expire, are shown once and can be revoked in the app console | | Scopes | Default, wsReadOnly, wsReadWrite, amReadOnlyWorkflow, amReadWriteWorkflow, amReadOnlyInvitation, amReadWriteInvitation, amReadOnlyGroup, amReadWriteGroup, amReadOnlyUser, amReadWriteUser, plus amReadOnlyAccessRole and dataExportFull on some methods | | Rate limits | About 400 requests a minute per IP or access token, answered with 429 too_many_requests. A second 429, rate_limit_exceeded, comes from overload protection | | Pagination | `pageSize` up to 1,000 with `nextPageToken`, a `limit` parameter, sort fields, date and assignee filters, and a `fields` array for optional data | | Errors | JSON body with `error` and `errorDescription`. 11 documented codes across 400, 401, 403, 404, 429 and 500 | | Batch | POST /batch schedules up to 100 independent operations as an async job with per-operation results | | Webhooks | Account, folder and space webhooks with event filtering, optional HMAC SHA-256 signing, up to 3 delivery attempts and automatic suspension | | Free tier | Free plan at $0 with the API and MCP server, 2 GB of storage per account. 14-day trial of paid plans with no card | | Audit | MCP actions appear in the activity stream under the authenticated user. User audit reports are on Pinnacle and Apex only | | Certifications | SOC 2 Type II, ISO 27001, 27017, 27018 and 27701 per the trust centre at security.wrike.com | | Status | status.wrike.com, Wrike's own page, a dated timeline of incidents and maintenance back to 2024 with no per-component view | | Sub-processors | List updated 2 July 2026 with locations. Hosting on AWS, Google Cloud and Microsoft Azure in the US or EU by region. AI processing by Microsoft Azure OpenAI, Google, Anthropic and OpenAI | | Capabilities | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting, automation.webhooks | | Tags | official, hosted, mcp, oauth, openapi, llms-txt, webhooks, freemium, free-tier, no-card, closed-source, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/wrike.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 68 | 13.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 78 | 12.7 | | Agent ergonomics | 13% | 16.2 | 63 | 10.2 | | Security & auth | 14% | 17.5 | 60 | 10.5 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 63 | 5.5 | | Transparency & trust (editorial 62, provenance 94) | 7% | 8.8 | 78 | 6.8 | | Negative events | up to −15 | up to −15 | 17 September 2026. The API changelog says the task dependency endpoints 'now' need the TaskDatesAndDependenciesEdit right and reject callers without it with 403, with no earlier notice found. The change is documented with the action required, so the smallest deduction applies (https://developers.wrike.com/changelog/permission-checks-enforced-on-task-dependency-endpoints). | -3 | | **Total** | | | | **60.1 → C** | ### Why each score - Reliability 68: Graded on the hosted lines for REST API v4 and the MCP server. status.wrike.com is Wrike's own page with a dated timeline back to 2024 but no per-component history and no API or MCP entry (15 of 20). In the 90 days to 8 October 2026 it shows three incidents, a 7-minute workspace loading problem on the EU data centre on 5 October, the mobile apps unreachable from 09:19 to 15:59 UTC on 12 September while web and desktop kept working, and an attachment upload fault for some users on 12 August. None names the API (20). The error reference gives 400 requests a minute per IP or access token (15). The FAQ advises exponential backoff on 429, with no Retry-After header and no idempotency keys for writes found (8 of 15). No SLA found in the terms, pricing or trust centre pages we read (0). API v4 is generally available and MCP v2 carries no beta label, though `recommend_resources` is a Wrike Labs tool (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 78: Each of the 244 API reference pages embeds an OpenAPI 3.0.1 definition with a bearer security scheme, and a Postman collection is published. We found no single downloadable spec (22 of 25). llms.txt and Markdown copies of every docs page (10). API parameter descriptions are short, such as 'Title of task, required', and the MCP tools page gives one line per tool with a few limits stated, for example that `prefill_requestform` doesn't submit. The MCP tool schemas sit behind authentication and were not read (12 of 20). Enums for status, importance and sort fields and required flags, but structured values such as dates travel as JSON strings in query parameters (11 of 15). Curl and JSON examples in the guides and an error table of 11 codes, while reference responses are grouped as 2XX, 4XX and 5XX (10 of 15). A single v4 version and a dated changelog with sparse entries (13 of 15). - Agent ergonomics 63: 29 MCP tools in a fixed set with no toolsets or read-only subset on the server (15 of 25). Task queries take `pageSize` up to 1,000, `nextPageToken`, sort fields, a `fields` array and filters for dates, assignees and status, and `search_items` filters by assignee, status, dates and importance (20). Errors return `error` and `errorDescription` from 11 documented codes, which name the fault but rarely the fix (14 of 20). No idempotency keys. The tools page marks each tool Read or Write, and whether the server sends readOnlyHint or destructiveHint was not checked. The async Batch API reports per-operation results (6 of 20). Creating a task needs only a title, but the FAQ says there is no official SDK (8 of 15). - Security & auth 60: OAuth 2.0 authorisation code flow with read-only and read-write scopes, one-hour access tokens and revocation. Permanent tokens never expire and reach everything their user can, and the docs point clients that need dynamic client registration to them. The docs also allow the token as an `access_token` query parameter, which costs 10 (20 of 30). The API has wsReadOnly, the MCP server inherits the user's permissions, has no delete tool and marks tools Read or Write, and client admins can restrict tools. No server-side read-only mode or confirmation step is documented (12 of 20). Comments, descriptions and inbox items written by other people reach the model, and no injection guidance was found (3 of 15). MCP actions appear in the activity stream under the user, and user audit reports are limited to Pinnacle and Apex (10 of 15). Valid security.txt with a report form, SOC 2 Type II and ISO 27001, 27017, 27018 and 27701 on the trust centre. No bug bounty or public advisories found (15 of 20). - Payments & pricing 30: No x402, MPP or L402 (0). Plan prices are public, Free $0, Team $10 and Business $25 a user a month, with Pinnacle and Apex quoted by sales. API calls aren't priced (10). The Free plan includes the API and the MCP server, and the 14-day trial needs no card (20). A person signs up in a browser and creates the API app or token (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 63: The newest API changelog entries are dated 17 September 2026, and the MCP tools page was updated on 7 October 2026 (30). Three dated changelog entries in the 90 days to 8 October, on 28 July and two on 17 September (20). A public changelog, a developer community forum and a support form. We didn't check response times (10 of 15). No official SDK, and the official MCP registry lists only a third-party server, ai.waystation/wrike (0). No packages to assess. The MIT agent skills repository is published by CI and last changed on 7 October 2026 (3 of 10). - Transparency & trust 78: Closed service with terms naming Wrike, Inc., and MIT agent skills (15). The privacy policy of 1 June 2026 gives retention periods but excludes customer data, which falls under the terms and a published DPA. The terms say customer data isn't used to train Wrike AI models, deletion follows 'then-current practices', and inactive Free accounts are deleted after 180 days. The MCP docs say the server stores and caches nothing (22 of 30). No deprecation policy found. The FAQ records the v3 sunset on 30 June 2019, and one parameter is marked deprecated without a date (5 of 20). The sub-processor list, updated 2 July 2026, gives purposes and US or EU locations by region (20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/wrike.md (JSON https://www.anchorterminal.com/fixes/wrike.json) ### What we couldn't check - unchecked: the MCP server's tool schemas and annotations (readOnlyHint, destructiveHint), because tools/list needs a Wrike account. The tool count of 29 is from the docs page. - unchecked: whether Wrike gave earlier notice by email of the 17 September 2026 permission change on dependency endpoints. - unchecked: the DPA and the information security addendum PDFs, and whether any enterprise contract carries an uptime SLA. - unchecked: response times on the developer community forum. - No single downloadable OpenAPI file was found. The definitions are embedded per reference page, so `openapi` is left empty. - The launch dates of MCP v1 and v2 were not found. A Wrike blog post on the MCP server is dated 6 October 2025. - security.txt expires on 10 October 2026 and will read as expired unless renewed. ### Sources - developer docs index (llms.txt): (seen 2026-10-08) - API v4 overview and scopes: (seen 2026-10-08) - OAuth 2.0 and permanent tokens: (seen 2026-10-08) - API errors and rate limit: (seen 2026-10-08) - FAQ (plans, rate limit, SDKs): (seen 2026-10-08) - MCP server overview: (seen 2026-10-08) - MCP tools: (seen 2026-10-08) - MCP permanent token setup: (seen 2026-10-08) - MCP setup for other clients: (seen 2026-10-08) - Create Task reference with OpenAPI: (seen 2026-10-08) - Query Tasks reference: (seen 2026-10-08) - webhooks: (seen 2026-10-08) - API changelog: (seen 2026-10-08) - changelog entry on dependency permission checks: (seen 2026-10-08) - status timeline feed: (seen 2026-10-08) - pricing: (seen 2026-10-08) - plan comparison table: (seen 2026-10-08) - help centre article on MCP: (seen 2026-10-08) - trust centre: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - terms: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - sub-processors: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - agent skills repository: (seen 2026-10-08) ## Who's behind it (provenance 94/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Wrike, Inc. | 20/20 | | Domain age | wrike.com, registered 2005-10-15 (20 years) | 15/15 | | Endpoint on the vendor's domain | www.wrike.com | 15/15 | | Terms of service | read, states 7 of the 7 things a reader expects, and has 3 clauses that cost points | 4/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.wrike.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The terms name Wrike, Inc. or its affiliate on the order, with a principal office at 550 West B Street, Floor 4, PMB 2305, San Diego, CA 92101, and apply to orders effective on or after 8 April 2025. The API answers on wrike.com hosts (www, app-eu, app-us2) and the MCP server at mcp.wrike.com. www.wrike.com/.well-known/security.txt names a report form and appsec@team.wrike.com and expires on 10 October 2026, two days after this check. RDAP for wrike.com gives a registration date of 2005-10-15. status.wrike.com/history redirects to a 404 page. The timeline is read from status.wrike.com/json, the feed the page itself loads. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.wrike.com/security/terms/), read 2026-10-08, dated 2025-04-08, states 7 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "access or search the Service by any means other than Wrike’s publicly supported interfaces (e.g., “scraping”)" - To know. Restricts benchmarking or competitive use (costs points). "if Customer is a Wrike competitor, use the Service directly or indirectly for competitive benchmarking or other competitive analysis" - To know. Says the terms or the service can change without notice (costs points). "for legal or regulatory reasons or for any other reasons as Wrike deems necessary, at its sole discretion, without notice." - To know. Says access can be ended without notice or for any reason. "Wrike may, with or without prior notice, immediately terminate the Agreement, Customer’s Account, Subscriptions and/or corresponding Subscription Term, and/or access to the Service and/or Add-Ons." - Gives the date it was last updated. Last updated 2025-04-08. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at $100. - Says how changes to the terms are announced. Says it gives notice of a change. - Also in the text (2026-10-08). Prompts and generated content from Wrike AI are stored temporarily by Microsoft Azure OpenAI Service for abuse monitoring. "For the avoidance of doubt, Customer is aware and accepts that, in connection with Customer’s use of Wrike AI, the Azure OpenAI Service will temporarily store all prompts and generated content to monitor for and prevent abusive or harmful uses or outputs of the Azure OpenAI Service." - Also in the text (2026-10-08). Export of customer data may be unavailable or limited after an account is deactivated or converted to a free account. "Customer may not be able, or may have limited ability, to export Customer Data after deactivation of its Customer Account or conversion to a Free Customer Account" - Also in the text (2026-10-08). Subscriptions renew automatically at the then-current rates unless the customer gives written notice before the term ends. "The Subscription will automatically renew for successive Subscription Terms at Wrike’s then-current rates unless Customer provides written notice of its intent not to renew such Subscription prior to the expiration of the then-current Subscription Term." **Privacy policy** (https://www.wrike.com/security/privacy/), read 2026-10-08, dated 2026-06-01, states 8 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Ad Targeting: We and our advertising partners use these cookies mainly to build a profile of your interests and show you relevant ads on other websites and deliver other online or offline marketing to you." - Gives the date it was last updated. Last updated 2026-06-01. - Says how long data is kept. Names a period of 10 years. - Gives a privacy contact. Gives an email address, hidden from our reader by the page. - Says where data is transferred or stored. Relies on the Data Privacy Framework. - Also in the text (2026-10-08). Emails exchanged with Wrike sales staff, including third-party replies, may be processed with AI tools. "Sales representatives’ emails and related correspondence, including complete email chains and third-party responses to Wrike communications, may be processed using AI-enabled tools for the purposes described in this Privacy Policy." ## Live (updated 2026-10-08 18:20 UTC) - Right now: up, HTTP 401, 236 ms, checked 2026-10-08 18:20 UTC (get on `https://www.wrike.com/api/v4`, asks for auth) - Uptime 24h 100.0% (33 probes) · 30 days 100.0% (33 probes) · p50 182 ms · p95 236 ms - Vendor status page: unknown, no machine-readable status found - security.txt: valid, expires 2026-10-10T11:59:00Z - Watching changelog - Always current: https://www.anchorterminal.com/api/v1/live/wrike.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Free (API and MCP server included) | free | per seat per month | 2 GB of storage per account | | Team | $10 | per seat per month | 2 to 15 users, as shown on 2026-10-08 | | Business | $25 | per seat per month | 5 to 200 users, as shown on 2026-10-08 | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Official remote MCP server at https://mcp.wrike.com/v2 over Streamable HTTP, with 29 documented tools and no delete tool - REST API v4 and the MCP server are included on every plan, Free among them, and the 14-day trial needs no card - OpenAPI 3.0.1 definitions on each of 244 reference pages, plus llms.txt and Markdown copies of the docs - OAuth 2.0 authorisation code flow with read-only and read-write scopes and one-hour access tokens - SOC 2 Type II and ISO 27001, 27017, 27018 and 27701 named on the trust centre, and a valid security.txt ## Weaknesses - A permanent access token never expires and reaches everything its user can, and it is the documented route for clients that need dynamic client registration - The API accepts the access token as an `access_token` query parameter as a documented option - No SLA, idempotency keys or Retry-After header found in the reviewed documentation - No official SDK, and the official MCP registry lists only a third-party Wrike server (ai.waystation/wrike) - The status page is a single timeline with no API or MCP component, and user audit reports are limited to Pinnacle and Apex ## Before you call it (notes for agents) 1. Build API URLs from the `host` value returned by /oauth2/token. Accounts live on www.wrike.com, app-eu.wrike.com or app-us2.wrike.com, and the wrong host answers 401. 2. Use https://mcp.wrike.com/v2 only. The older /app/mcp/stream and /app/mcp/sse URLs serve the v1 tool set. 3. Call `search_workflows` before setting a status, because `update_items` and `search_items` take custom status ids. 4. Stay under about 400 requests a minute per token or IP and back off exponentially on 429. Use POST /batch for up to 100 operations. 5. Page task lists with `pageSize` (up to 1,000) and `nextPageToken`, and request optional data through `fields`. ## Connect First request: ```bash curl -X GET -H "Authorization: bearer $WRIKE_ACCESS_TOKEN" "https://www.wrike.com/api/v4/contacts?me=true" ``` MCP client configuration: ```json { "mcpServers": { "wrike": { "args": [ "mcp-remote", "https://mcp.wrike.com/v2", "--header", "Authorization:Bearer YOUR_ACCESS_TOKEN" ], "command": "npx" } } } ``` Through letme (picks today, calling later): https://letme.dev/wrike. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | monday.com | BB | 76.4 | 32 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/monday.md | | Asana | BB | 70.1 | 134 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/asana.md | | Todoist | B | 66.9 | 206 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/todoist.md | | ClickUp | C | 60.9 | 336 | tasks.create, tasks.update, projects.manage, tasks.comments, projects.reporting | no | https://www.anchorterminal.com/tools/clickup.md | | Trello | C | 61.1 | 333 | tasks.create, tasks.update, projects.manage, tasks.comments | no | https://www.anchorterminal.com/tools/trello.md | | Roma | D | 51.1 | 509 | tasks.create, tasks.update, projects.manage | no | https://www.anchorterminal.com/tools/roma.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - MCP v2 is served at https://mcp.wrike.com/v2 over Streamable HTTP only, with OAuth 2.0 through an OAuth app an admin creates, or a permanent access token sent as a Bearer header (source: ) - The tools page lists 29 tools marked Read or Write, among them search_items, get_item_details (up to five items), create_task_item, update_items (up to 20 items) and create_item_comment, with no delete tool (source: ) - The comparison table lists Open RESTful API and MCP Server on every plan from Free to Apex (source: ) - API errors list 429 too_many_requests at 400 requests per minute per IP or access token, and the FAQ advises exponential backoff (source: ) - An async Batch API takes up to 100 operations in one request, announced 30 December 2025 (source: ) - Webhooks can be signed with a shared secret (X-Hook-Signature, HMAC SHA-256), are retried up to 3 times and are suspended after failures (source: ) - Wrike publishes five agent skills for the MCP server under MIT at https://github.com/wrike/agent-skills ## Compare - [Asana vs Wrike](https://www.anchorterminal.com/compare/asana-vs-wrike.md): BB 70.1 vs C 60.1 - [ClickUp vs Wrike](https://www.anchorterminal.com/compare/clickup-vs-wrike.md): C 60.9 vs C 60.1 - [monday.com vs Wrike](https://www.anchorterminal.com/compare/monday-vs-wrike.md): BB 76.4 vs C 60.1 - [Roma vs Wrike](https://www.anchorterminal.com/compare/roma-vs-wrike.md): D 51.1 vs C 60.1 - [Todoist vs Wrike](https://www.anchorterminal.com/compare/todoist-vs-wrike.md): B 66.9 vs C 60.1 - [Trello vs Wrike](https://www.anchorterminal.com/compare/trello-vs-wrike.md): C 61.1 vs C 60.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on wrike.com or one of its subdomains, or the README of github.com/wrike/agent-skills. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "wrike", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Wrike on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Wrike on Anchor Terminal](https://www.anchorterminal.com/badges/wrike.svg)](https://www.anchorterminal.com/tools/wrike) ``` Plain link: ```html Wrike on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Wrike is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/wrike-dark.png - Light: https://www.anchorterminal.com/assets/share/wrike-light.png