# Harness Feature Management & Experimentation vs Woopra

> Harness Feature Management & Experimentation scores 69.2 (B) to Woopra's 44.4 (E) for event analytics. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/harness-fme-vs-woopra
- Markdown: https://www.anchorterminal.com/compare/harness-fme-vs-woopra.md (~4,800 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Harness Feature Management & Experimentation scores 69.2 (B) on agent readiness against Woopra's 44.4 (E), and leads in 4 of 7 scored categories. Woopra leads on payments & pricing. Both do event analytics.

- Harness Feature Management & Experimentation: grade B, 69.2/100, rank #258 of 1510. Markdown https://www.anchorterminal.com/tools/harness-fme.md · JSON https://www.anchorterminal.com/api/v1/tools/harness-fme.json
- Woopra: grade E, 44.4/100, rank #1219 of 1510. Markdown https://www.anchorterminal.com/tools/woopra.md · JSON https://www.anchorterminal.com/api/v1/tools/woopra.json
- Best product analytics and experimentation tools for AI agents: https://www.anchorterminal.com/best/product-analytics/index.md
- All 170 product analytics comparisons: https://www.anchorterminal.com/compare/product-analytics/index.md

## Which one, for what

### Harness Feature Management & Experimentation (B)

Good for: Teams already on Harness, or Split customers, who want agents to inspect and change flags and segments with guard rails.

Ahead on:
- Schema & documentation, 71 against 45
- Agent ergonomics, 83 against 45
- Security & auth, 79 against 22
- Maintenance & community, 81 against 9

Also in its favour:
- Runs on your own machine

Watch for: No FME prices are published; Enterprise is by quotation and free plan limits are unstated

### Woopra (E)

Good for: An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule.

Ahead on:
- Payments & pricing, 30 against 15

Watch for: Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference


## Why the edge

### Maintenance & community: Harness Feature Management & Experimentation +72

- Harness Feature Management & Experimentation (81): harness-mcp-v2 3.2.40 was tagged on 4 November 2026 (30). 14 tagged MCP releases between 8 August and 4 November (20). 100 commits since 8 August in the clone; FME docs and SDK release notes are dated, with support and a community site. Issue response times weren't read because the GitHub API refused us for its rate limit (15 of 25). Not found in the official MCP registry under a Harness namespace; official SDKs are current (8 of 15). MIT package with npm shrinkwrap and tests; CI state not read (8 of 10). 30+20+15+8+8 = 81.
- Woopra (9): The newest dated change found is a commit to the browser tracker on 16 March 2026, and the REST intro page was last edited on 13 March 2026, both more than 180 days before the check (0). No releases or dated changelog entries in the last 90 days (0). No API changelog. Support is by email and in-app, and response times were not checked (3). The browser tracker's last tag is v5.3.0 from 2021, iOS and Android were last committed to in November 2024, and the Node, Python, Java and Rails SDKs in 2017 (4). The Node README carries a Travis CI badge and no current CI was found (2). Total 9.

### Security & auth: Harness Feature Management & Experimentation +57

- Harness Feature Management & Experimentation (79): Admin API keys with combinable roles that can't be widened after creation, Harness PATs and SATs for central management, and Harness Platform OAuth on the hosted MCP endpoint. Credentials travel in headers (28 of 30). HARNESS_READ_ONLY removes every write, writes go through elicitation with a risk threshold for auto-approval, and FME change requests add approval for flag changes (19 of 20). No prompt-injection guidance; the tools return flag names, descriptions and rule data written by people (3 of 15). FME admin, environment and object audit logs, plus structured MCP audit events to file, webhook or OpenTelemetry sinks (13 of 15). SOC 1 and SOC 2 Type II, ISO 27001, 27017 and 27018, FedRAMP 20x, a security@harness.io disclosure route with a 24-hour response, a private bug bounty on request and annual external penetration tests. No security.txt (16 of 20). 28+19+3+13+16 = 79.
- Woopra (22): REST calls use per-user access keys sent by HTTP Basic, with no scopes or rotation guidance found. Tracking calls need only the project name by default, with an optional Secure Tracking secret. Docs examples still show `http://` tracking URLs (15 of 30). The pricing page states group and individual permission controls, but no read-only key or confirmation on `/profile/delete` was found (5). The API returns event and profile text that any caller who knows the project name can write, and no guidance on untrusted content was found (0). No audit log found in the docs (0). No security page, bug bounty or certification was found on the pages read, and security.txt timed out. The privacy policy states Data Privacy Framework certification (2). Total 22.

### Agent ergonomics: Harness Feature Management & Experimentation +38

- Harness Feature Management & Experimentation (83): 11 consolidated tools, and `--toolsets=fme` narrows the server to FME (25). Flag lists filter server-side by name, tag and rollout status, and the Admin API paginates with markerLimit (17 of 20). Documented status codes, 429 headers, and a harness_diagnose tool. Error bodies aren't documented per endpoint (14 of 20). harness_list and harness_get carry readOnlyHint, write tools ask for confirmation by elicitation, and harness_delete is marked destructive. No idempotency keys (15 of 20). Two required settings (API key, optional org and project, account ID read from the token); a Python Admin API wrapper and CLI, and SDKs in more than a dozen languages for evaluation (12 of 15). 25+17+14+15+12 = 83.
- Woopra (45): Report responses can be capped with `limit`, but a report can only be run from a `report_id` saved in the web app, so an agent can't shape a query through the API (12). `limit`, `offset`, a `snapshot` ID for consistent paging and timeframe overrides on reports, and position headers on log export (14). Tracking codes 401, 402 and 403 each name a cause. REST error bodies are not documented (8). No idempotency key or dedupe field was found, and tracking is by GET. Imports return a batch ID to poll (3). Report calls need two parameters. Official SDKs exist in several languages, but the server ones date from 2017 (8). Total 45.

### Schema & documentation: Harness Feature Management & Experimentation +26

- Harness Feature Management & Experimentation (71): No public OpenAPI file for the Admin API was found; the reference is a ReadMe site with a Postman collection. The MCP server's 11 tools have typed inputs, and harness_describe returns each FME resource's fields (18 of 25). llms.txt on both developer.harness.io and docs.split.io, and every page as Markdown with `.md` (10). The README describes each tool and when writes ask for confirmation; resource details sit behind harness_describe rather than in the tool text (13 of 20). The generic tools take a resource_type string and a body, so per-resource constraints aren't in the schema (8 of 15). An error-code page lists 400, 401, 402, 403, 404, 409 and 429 with causes, and docs carry curl examples (10 of 15). Tagged MCP releases and dated SDK versioning policy; the Admin API has v1 and v2 paths and deprecation notices for Split-era endpoints (12 of 15). 18+10+13+8+10+12 = 71.
- Woopra (45): Each REST reference page embeds an OpenAPI 3.1 fragment in its Markdown copy. No single spec file was found, most operations define no responses, and the tracking endpoints are documented as tables (12). llms.txt and a .md copy of each page, though llms.txt lists four of fourteen REST operations (10). Descriptions are one line. The `/profiles` page repeats the `/trends` text, three profile operations have none, and one page still holds template placeholder text (6). Query parameters carry types and required flags. There are no enums, and profile edits take a JSON string in `data` (6). One curl example for REST and several tracking examples. Tracking response codes are explained, while REST errors are a 400 with an empty object (6). The version sits in the path and 3.10 is the only one supported. No changelog found (5). Total 45.

### Payments & pricing: Woopra +15

- Harness Feature Management & Experimentation (15): No x402, MPP or L402 (0). No FME prices are published; harness.io/pricing lists FME only under Enterprise, priced by quotation (0). The docs describe a Start FME Free Plan step inside a Harness account; its limits and whether a card is needed aren't stated (15 of 20). A person signs up for Harness in a browser and creates a key or token (0). 0+0+15+0 = 15.
- Woopra (30): No x402, MPP or L402 (0). Pro is public at a starting price of $999 a month for 5 million events. Overage rates and Enterprise prices are not published (10). 30-day trial of Pro. The terms say a customer may add a card during the trial, which suggests none is needed to start, but we did not see the signup form (20). A person signs up in a browser and generates keys in the members area (0). Total 30.

## Score by category

| Category | Weight | Harness Feature Management & Experimentation | Woopra | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 80 | even |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 71 | 45 | Harness Feature Management & Experimentation +26 |
| Agent ergonomics | 13% (16.2 this run) | 83 | 45 | Harness Feature Management & Experimentation +38 |
| Security & auth | 14% (17.5 this run) | 79 | 22 | Harness Feature Management & Experimentation +57 |
| Payments & pricing | 10% (12.5 this run) | 15 | 30 | Woopra +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 81 | 9 | Harness Feature Management & Experimentation +72 |
| Transparency & trust | 7% (8.8 this run) | 61 | 62 | Woopra +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **69.2 · B** | **44.4 · E** | |

## Facts side by side

| Fact | Harness Feature Management & Experimentation | Woopra |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Harness Inc. | Woopra, Inc. |
| Hosted endpoint | `https://mcp.harness.io/mcp` | `https://www.woopra.com/rest/3.10` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| Price for event analytics | not published | $999 per month (plan) |
| x402 | no | no |
| Licence | none | Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC |
| Tools exposed | 11 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-04 | 2026-03-16 |
| Terms last updated | no date given | 2025-12-10 |
| Privacy policy last updated | no date given | 2025-08-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 8.8k npm/wk | 415 npm/wk |
| Agent reviews | none | 2.3/5 (4) |

## How the scores have moved

### Harness Feature Management & Experimentation

No score change since it was listed.

### Woopra

- -0.1 on 28 October 2026: correction
- +0.1 on 27 October 2026: checklist

## Verdicts

**Harness Feature Management & Experimentation.** Harness FME, formerly Split, gives agents 11 consolidated MCP tools with an FME-only toolset, a read-only switch and confirmation on writes, over an Admin API with documented limits and role-scoped keys. FME prices are not published, the free plan's limits are unstated, and the hosted MCP endpoint must be enabled by Harness Support.

**Woopra.** Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found.

## Before you call either

### Harness Feature Management & Experimentation

1. Start the MCP server with `--toolsets=fme` so only FME resource types load
2. Call `harness_describe(resource_type='fme_feature_flag')` before a create or update to see the fields
3. Filter fme_feature_flag lists by name, tags or rollout status rather than listing every flag
4. Set HARNESS_READ_ONLY for analysis tasks; leave confirmation on for kill, restore and delete
5. On 429, wait at least the larger X-RateLimit-Reset-Seconds value before retrying

### Woopra

1. Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as `report_id`
2. Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against `https://www.woopra.com/rest/3.10/`
3. Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule
4. Reuse the `snapshot` ID from the first response when paging with `offset`, or pages past 1,000 records may not agree
5. Send `cookie` or a `cv_` identifier such as `cv_email` on every track call. Without one the event lands on a random profile that can't be identified later
6. When reading `/logs/export`, delete the profile named in each `type: "delete"` line. The following lines log its data again under `new_id`

## Questions

### Which is better for AI agents, Harness Feature Management & Experimentation or Woopra?

Harness Feature Management & Experimentation scores 69.2 (B) on agent readiness against Woopra's 44.4 (E), and leads in 4 of 7 scored categories. Woopra leads on payments & pricing.

### Do Harness Feature Management & Experimentation and Woopra need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Harness Feature Management & Experimentation and Woopra without installing anything?

Yes. Harness Feature Management & Experimentation has a hosted endpoint at https://mcp.harness.io/mcp and Woopra at https://www.woopra.com/rest/3.10.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/harness-fme-vs-woopra.json, and with the fewest tokens: https://www.anchorterminal.com/compare/harness-fme-vs-woopra.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "harness-fme", "b": "woopra"}`. From a terminal: `anchor compare harness-fme woopra`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/harness-fme.json and https://www.anchorterminal.com/api/v1/tools/woopra.json

## Other comparisons with Harness Feature Management & Experimentation or Woopra

- [Amplitude vs Woopra](https://www.anchorterminal.com/compare/amplitude-vs-woopra.md)
- [Basedash MCP vs Woopra](https://www.anchorterminal.com/compare/basedash-mcp-vs-woopra.md)
- [Countly vs Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md)
- [Fullstory vs Woopra](https://www.anchorterminal.com/compare/fullstory-vs-woopra.md)
- [GrowthBook vs Woopra](https://www.anchorterminal.com/compare/growthbook-vs-woopra.md)
- [Matomo vs Woopra](https://www.anchorterminal.com/compare/matomo-vs-woopra.md)
- [Mixpanel vs Woopra](https://www.anchorterminal.com/compare/mixpanel-vs-woopra.md)
- [Mostly Good Metrics vs Woopra](https://www.anchorterminal.com/compare/mostly-good-metrics-vs-woopra.md)
- [OpenPanel vs Woopra](https://www.anchorterminal.com/compare/openpanel-vs-woopra.md)
- [Optimizely Experimentation vs Woopra](https://www.anchorterminal.com/compare/optimizely-vs-woopra.md)
- [Pendo vs Woopra](https://www.anchorterminal.com/compare/pendo-vs-woopra.md)
- [PostHog vs Woopra](https://www.anchorterminal.com/compare/posthog-vs-woopra.md)
- [Statsig vs Woopra](https://www.anchorterminal.com/compare/statsig-vs-woopra.md)
- [Userpilot vs Woopra](https://www.anchorterminal.com/compare/userpilot-vs-woopra.md)
- [Flagsmith vs Woopra](https://www.anchorterminal.com/compare/flagsmith-vs-woopra.md)
- [Fullstory vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/fullstory-vs-harness-fme.md)
- [Harness Feature Management & Experimentation vs Heap](https://www.anchorterminal.com/compare/harness-fme-vs-heap.md)
- [Harness Feature Management & Experimentation vs OpenPanel](https://www.anchorterminal.com/compare/harness-fme-vs-openpanel.md)
- [Harness Feature Management & Experimentation vs RudderStack MCP](https://www.anchorterminal.com/compare/harness-fme-vs-rudderstack-mcp.md)
- [Heap vs Woopra](https://www.anchorterminal.com/compare/heap-vs-woopra.md)
- [RudderStack MCP vs Woopra](https://www.anchorterminal.com/compare/rudderstack-mcp-vs-woopra.md)
- [Amplitude vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/amplitude-vs-harness-fme.md)
- [Countly vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/countly-vs-harness-fme.md)
- [Flagsmith vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/flagsmith-vs-harness-fme.md)
- [Harness Feature Management & Experimentation vs LaunchDarkly](https://www.anchorterminal.com/compare/harness-fme-vs-launchdarkly.md)
- [Harness Feature Management & Experimentation vs Mixpanel](https://www.anchorterminal.com/compare/harness-fme-vs-mixpanel.md)
- [Harness Feature Management & Experimentation vs Optimizely Experimentation](https://www.anchorterminal.com/compare/harness-fme-vs-optimizely.md)
- [Harness Feature Management & Experimentation vs PostHog](https://www.anchorterminal.com/compare/harness-fme-vs-posthog.md)
- [Harness Feature Management & Experimentation vs Statsig](https://www.anchorterminal.com/compare/harness-fme-vs-statsig.md)
- [GrowthBook vs Harness Feature Management & Experimentation](https://www.anchorterminal.com/compare/growthbook-vs-harness-fme.md)
- [Harness Feature Management & Experimentation vs Matomo](https://www.anchorterminal.com/compare/harness-fme-vs-matomo.md)
- [Harness Feature Management & Experimentation vs Mostly Good Metrics](https://www.anchorterminal.com/compare/harness-fme-vs-mostly-good-metrics.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp